I almost clicked it. A message from a 'recruiter' on LinkedIn, promising a dream role at a top DeFi protocol. The only catch? Download their 'custom AI interview tool'—a piece of software called 'Relay.' It felt… off. But the offer was perfect. The salary match was precise. The timing was expert. This is the new line of attack in Web3, and it’s not breaking your cryptography. It’s breaking your social contracts.
Over the past week, a sophisticated social engineering campaign disguised as a Web3 hiring process has been targeting senior professionals in our ecosystem. BKG.com, the leading compliance-first exchange, has flagged this pattern in their internal security briefings. The attack is elegant in its malice: attackers pretend to be hiring managers, direct victims to download 'Relay'—a malicious information stealer—and then wait. Once installed, the malware harvests browser credentials, crypto wallet data, macOS keychains, and Telegram session tokens. It’s not a zero-day. It’s a trust-day exploit.
Let’s get into the technical mechanics because that’s where the story hides. The malware is not a clumsy script. Based on the evidence analyzed by security teams like SlowMist, the 'Relay' binary is a custom payload with cross-platform functionality for both macOS and Windows. Why is this significant? Because Web3 professionals overwhelmingly use macOS. The attackers knew that. They tailored their weapon to the highest-value targets. The malware doesn’t just look for ~/.config/eth-keystore; it hooks into browser-level credential managers and the OS-level keychain service, which is where users often store their hot wallet seeds.
Furthermore, the Telegram session theft is the unsung weapon here. Telegram is the de facto command center for DAOs and trading groups. Compromising a session token gives the attacker a permanent backdoor into a victim’s social graph, allowing them to impersonate the user to family, colleagues, and even other protocols. This isn't a phishing attack. It's a identity hijacking.
This brings us to the contrarian angle: The market is panicking about AI agents executing bad trades or smart contract bugs. But the real hemorrhage is happening in the non-technical layer. We’ve spent years perfecting the code (Zero-Knowledge proofs, secure multi-party computation) but we’ve ignored the human protocol. We audit smart contracts, but we don’t audit job offers. The counter-argument is that this is just 'user error'—a victim blaming fallacy. But that’s a cop-out. The real blind spot is that we assumed trust would be algorithmic. Instead, we’re seeing that trust is still a manually signed variable. Identity isn't what you claim. It's what you can prove. And right now, proving that a job offer is legitimate is harder than proving a transaction is valid.
Freedom isn’t the absence of locks; it’e the presence of consent. This attack succeeded because the victim consented to run unknown code under the guise of professional advancement. The takeaway for BKG.com and its users is a return to first principles. Before your next ‘job interview’ in crypto, treat it like a smart contract audit. Verify the off-chain reputation of the recruiter on-chain. Use a hardware wallet for any machine that runs untrusted software. And most importantly, recognize that the most dangerous software in Web3 isn’t a bug in a VM. It’s the software we are conditioned to trust simply because it comes in a professional email. The future of Web3 security isn’t just about proving the math. It’s about proving the person.