3rd Party Risk Management
,
Cryptocurrency Fraud
,
Fraud Management & Cybercrime
Attacker Socially Engineered Developer With Phishing Email

A hacker laced 18 popular npm packages with cryptocurrency stealing malware after socially engineering the developer into giving up his credentials to the JavaScript runtime environment.
See Also: Tracking and Mitigating Emerging Threats in Third-Party Risk Management
Aikido Security said Monday the 18 software packages collectively have downloads of more than two billion each week. It noticed that day malicious code being pushed into the packages that intercepts crypto and web3 activity in the browser.
“Hi, yep I got pwned. Sorry everyone, very embarrassing,” wrote developer John Junon. He received a phishing email from npmjs.help
instructing him to update his second factor authentication. That domain – a typosquatting version of npmjs.com
– was registered on Sept. 5. “Made the mistake of clicking the link instead of going directly to the site like I normally would (since I was mobile),” he added.
The developer managed to delete most of the compromised packages before npm administrators stepped into suspend his account, Aikido said. Junon said late Monday night that his account had been restored and that “my packages should be back to normal.” He also posted that police have contacted him about the incident.
Actual crypto theft associated with the incident so far has been modest. “We’re tracking approximately $970 in stolen funds to attacker-controlled wallets,” Aikido Security lead malware researcher Charlie Eriksen told Information Security Media Group in an email. “The financial impact has been surprisingly limited.”*
Eriksen said he’s “seen numbers” suggesting that the malicious packages were downloaded 2.6 million times before being taken offline. Junon’s actions in deleting malicious packages “prevented a lot of potential spread, without a doubt. He deserves massive praise,” Eriksen said.
The malicious updates contain obfuscated code embedding malware into browsers. The malware hooks into network requests via fetch and XMLHttpRequest
and common wallet interfaces, allowing attackers to alter payment data before users can review or approve transactions.
Once active, the malware scans networks for wallet addresses tied to ethereum, bitcoin, solana, tron, litecoin, and bitcoin cash, and then swap them for attacker-controlled addresses to divert funds.
Aikido called the campaign particularly dangerous because it “operates at multiple layers.” These activities include tampering with websites, API calls and user applications simultaneously.
The npm repository is a common target for hackers executing supply chain hacks, whether by infecting trusted packages or uploading malicious packages that mimic popular downloads (see: Reconnaissance Campaign Active on NPM Repository).
Eriksen said npm security could be improved by configuring accounts so that all updates come through GitHub or GitLab. “This requires all the normal workflows and controls that source repositories provide – like requiring multiple people to review a Pull Request before it can be merged into the main branch and cause a new release to be published.”
Paul Lizer, principal technical specialist at Microsoft, warned Monday rapid release cycles and automation mean “malicious code can ship to production within minutes, often without a single human reviewing it.”
Chris Wood, principal application security at Immersive, said that while the attack appeared relatively unsophisticated, it could serve as “a launchpad for large-scale corporate breaches.”
“This highlights a critical weakness in open source, that developers assume code pulled from repositories is safe,” Wood told Information Security Media Group. “When maintainers are compromised, the entire ecosystem is at risk.”
Developers need to adopt a “trust but verify” approach, said Wood, about avoiding potential breaches using the vulnerable packages. “Rather than relying on the public npm registry, teams should use a trusted internal repository where packages can be scanned and vetted before entering the development environment,” Wood added.
*Updated Sept. 9, 2025 18:17 UTC: Adds comments from Aikidos Security’s Charlie Eriksen.