BRIDGEHEAD: An npm typosquatting campaign that crosses from WSL into Windows to plant a crypto-wallet stealer
In August 2026, a typosquatting campaign named BRIDGEHEAD targeted npm users by publishing 40 malicious packages mimicking popular libraries. These packages contained install scripts that detect Windows or WSL environments and download a Rust-based executable that runs in memory to steal cryptocurrency wallets, browser credentials, cookies, and Telegram sessions. The campaign crosses from WSL into Windows, leveraging legitimate services for stealthy reconnaissance and data exfiltration. Although the npm packages were removed quickly, the GitHub-hosted payload and command-and-control infrastructure remained active for days, complicating mitigation.
AI Analysis
Technical Summary
BRIDGEHEAD is a supply-chain typosquatting campaign that distributed 40 malicious npm packages impersonating well-known libraries such as chalk, axios, and lodash. Upon installation, these packages profile the host environment and, if Windows or Windows Subsystem for Linux (WSL) is detected, download a 22MB Rust-based payload from GitHub. This payload executes entirely in memory without writing files to disk, targeting sensitive data including cryptocurrency wallets, browser credentials, cookies, and Telegram sessions. The malware uses legitimate services for reconnaissance and exfiltration to evade detection and takedown efforts. While the npm packages were removed within 84 minutes, the payload hosted on GitHub persisted for 39 hours, and the command-and-control server remained operational beyond that. The campaign specifically exploits the boundary between WSL and Windows to compromise developer environments.
Potential Impact
The campaign enables attackers to steal high-value credentials and cryptocurrency wallets from compromised developer machines. By executing the payload in memory and leveraging legitimate services for communication, it reduces the likelihood of detection and removal. The persistence of the GitHub-hosted payload and command-and-control infrastructure after removal of the npm packages increases the window of exposure. This can lead to significant credential theft, session hijacking, and financial loss for affected users.
Mitigation Recommendations
The malicious npm packages were removed within 84 minutes, but the GitHub-hosted payload and command-and-control servers remained active for longer periods. Users should ensure they do not install packages from untrusted or suspicious sources, especially typosquatted packages mimicking popular libraries. Monitoring for unusual network activity related to GitHub-hosted executables and blocking known command-and-control domains can help reduce risk. Since this is a supply-chain attack vector, verifying package integrity and using package signing or lockfiles is recommended. Patch status is not applicable as this is a campaign leveraging social engineering and supply-chain abuse rather than a software vulnerability.
Indicators of Compromise
- hash: 6f088ade49456db2422c3edfbb9998f4a3e9cce7c4c00a7279fb45d672a82b7d
- hash: 52c11f246309cce5556a00408bafb9868622114903dbd8128dc4ce3eca2df27a
- hash: 6888d4c54ef2b5bf23889f9637c2efe77e1d2af4724d315b73d646cf5547dc73
BRIDGEHEAD: An npm typosquatting campaign that crosses from WSL into Windows to plant a crypto-wallet stealer
Description
In August 2026, a typosquatting campaign named BRIDGEHEAD targeted npm users by publishing 40 malicious packages mimicking popular libraries. These packages contained install scripts that detect Windows or WSL environments and download a Rust-based executable that runs in memory to steal cryptocurrency wallets, browser credentials, cookies, and Telegram sessions. The campaign crosses from WSL into Windows, leveraging legitimate services for stealthy reconnaissance and data exfiltration. Although the npm packages were removed quickly, the GitHub-hosted payload and command-and-control infrastructure remained active for days, complicating mitigation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
BRIDGEHEAD is a supply-chain typosquatting campaign that distributed 40 malicious npm packages impersonating well-known libraries such as chalk, axios, and lodash. Upon installation, these packages profile the host environment and, if Windows or Windows Subsystem for Linux (WSL) is detected, download a 22MB Rust-based payload from GitHub. This payload executes entirely in memory without writing files to disk, targeting sensitive data including cryptocurrency wallets, browser credentials, cookies, and Telegram sessions. The malware uses legitimate services for reconnaissance and exfiltration to evade detection and takedown efforts. While the npm packages were removed within 84 minutes, the payload hosted on GitHub persisted for 39 hours, and the command-and-control server remained operational beyond that. The campaign specifically exploits the boundary between WSL and Windows to compromise developer environments.
Potential Impact
The campaign enables attackers to steal high-value credentials and cryptocurrency wallets from compromised developer machines. By executing the payload in memory and leveraging legitimate services for communication, it reduces the likelihood of detection and removal. The persistence of the GitHub-hosted payload and command-and-control infrastructure after removal of the npm packages increases the window of exposure. This can lead to significant credential theft, session hijacking, and financial loss for affected users.
Defensive Guidance
The malicious npm packages were removed within 84 minutes, but the GitHub-hosted payload and command-and-control servers remained active for longer periods. Users should ensure they do not install packages from untrusted or suspicious sources, especially typosquatted packages mimicking popular libraries. Monitoring for unusual network activity related to GitHub-hosted executables and blocking known command-and-control domains can help reduce risk. Since this is a supply-chain attack vector, verifying package integrity and using package signing or lockfiles is recommended. Patch status is not applicable as this is a campaign leveraging social engineering and supply-chain abuse rather than a software vulnerability.
Technical Details
- Author
- AlienVault
- Tlp
- white
- References
- ["https://www.cloudsek.com/blog/bridgehead-npm-typosquatting-wsl-windows-crypto-wallet-stealer"]
- Adversary
- null
- Pulse Id
- 6a8734846b4cc1afd4bde567
- Threat Score
- null
Indicators of Compromise
Hash
| Value | Description | Copy |
|---|---|---|
hash6f088ade49456db2422c3edfbb9998f4a3e9cce7c4c00a7279fb45d672a82b7d | — | |
hash52c11f246309cce5556a00408bafb9868622114903dbd8128dc4ce3eca2df27a | — | |
hash6888d4c54ef2b5bf23889f9637c2efe77e1d2af4724d315b73d646cf5547dc73 | — |
Threat ID: 6a878fb4acd9273b49493df2
Added to database: 08/20/2026, 23:37:24 UTC
Last enriched: 08/20/2026, 23:56:32 UTC
Last updated: 08/21/2026, 00:41:26 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.