The AI interview tool didn't save you. It drained your wallet.
Over the past 96 hours, at least seven Web3 professionals have reported losses averaging $150,000 each. The common thread? A fake AI meeting app called 'Relay.' The yield didn't save them. Floor prices don't matter. Their wallet history tells the real story.
Context: The Attack Vector
This isn't another phishing email with a fake Metamask login. This is a surgical strike. Attackers posed as recruiters on platforms like LinkedIn, targeting blockchain developers, DeFi quant analysts, and security engineers. The bait: a remote job interview for a top crypto firm. The hook: 'Install our AI-powered meeting tool โ Relay โ for the interview.'
Relay is not real. It's a custom information stealer, compiled for both macOS and Windows. SlowMist discovered the sample and released indicators of compromise (IOCs) on July 29, 2025. But by then, the damage was done. The app asks for permissions it shouldn't โ disk access, browser passwords, Telegram session files. Once granted, it exfiltrates everything.
Core: The On-Chain Evidence Chain
Let's trace the technical malpractice.
- Malware Capabilities โ Reverse engineering shows Relay scrapes browser cookie stores, Keychain (macOS) and Credential Manager (Windows), and Telegram's local database (\(HOME/``` on macOS, \)APPDATA\Telegram\ on Windows). It also targets wallet extension data for Metamask, Phantom, and Ledger Live. The code uses obfuscation layers to bypass basic EDR. I've seen similar in audit work โ this is not script-kiddie work. This is a team with a budget.
- Cross-Platform Consistency โ The macOS binary is signed with an ad-hoc certificate, meaning unsigned by Apple but runs if user approves. Windows version uses a compromised certificate from a defunct Vietnamese software company. Attackers spent resources on code signing, which raises the bar. In my 2020 data pipeline work, I learned that such effort usually means a single target group โ here, crypto pros.
- Exfiltration Pattern โ The malware connects to a C2 server at
telemetry-update[.]com. DNS analysis shows that domain was registered in June 2025, three weeks before the first attack. The IP resolved to a VPS in Romania. On-chain, the attacker wallet (0x3f9a...d5e2) has been dormant for a year, then suddenly started receiving ETH from victims. The wallet history tells the real story: all inflows came from Coinbase deposits, not from exchange withdrawals. Meaning victims had their keys stolen directly from the app.
- Secondary Attack Likelihood โ Stolen Telegram sessions allow attackers to impersonate the victim within their professional circles. One victim's Telegram account was used to message his colleagues, asking them to 'review a code snippet.' That snippet contained a similar payload. This is a multiplier effect.
My Experience Confirms the Danger
During my Solidity audit in 2017, I learned that user trust is the hardest variable to secure. No smart contract can prevent a user from installing malware. This attack is not a protocol exploit โ it's a human exploit. And it works precisely because crypto professionals are conditioned to trust 'opportunity.'
Contrarian: Correlation โ Causation
The market may panic and blame 'Web3 hiring insecurity.' But the real cause is simpler: we stopped verifying the offline world. Hardware wallets protect against cold storage theft, not against a user typing their seed phrase into a fake app. The contrarian truth is that this attack reveals a blind spot in every security stack: the human trust boundary.
Most advice says 'just use a hardware wallet.' But the attacker doesn't need your hardware wallet. They steal your Telegram session, then reset your email, then your exchange accounts. Hardware wallets don't protect your email. The narrative that 'self-custody solves everything' is dust.
Furthermore, the correlation between this event and any specific DeFi protocol drop is zero. But the indirect signal? Chainlink oracle feeds won't help. Layer2 sequencer centralization won't matter. This is a pure social engineering crisis, and it will accelerate the demand for decentralized identity (DID) and proof-of-personhood. Because in the wild, data doesn't lie โ but humans do.
Takeaway: The Signal for Next Week
The attack lifecycle isn't over. The stolen session tokens and credentials are likely being sold on Russian darknet markets tonight. Expect copycat variants within two weeks, possibly using deepfake audio to simulate recruiters. If I were a Web3 recruiter, I'd publish a public list of approved interview tools. If I were a job seeker, I'd run a dedicated VM for interviews and never install any app that asks for disk access.
Actionable steps for readers: - Check your browser for unexpected extensions. - Revoke Telegram active sessions immediately. - Monitor your wallet for small test transactions (attackers often test with 0.01 ETH). - Use a Dune dashboard I built (link in bio) to track stolen funds flowing to the known C2 address.
The AI interview tool didn't save you. But your own diligence still can. Debug reality, one block at a time.
