New IronWorm malware hits 36 packages in npm supply-chain attack
A new supply-chain attack has infected 36 packages on the Node Package Manager (npm) index with infostealer malware called IronWorm. [...]
AI Analysis
Technical Summary
IronWorm is a Rust-based infostealer malware involved in a supply-chain attack targeting 36 packages on the npm registry. It steals sensitive environment variables and credential files including those for OpenAI, AWS, Anthropic, npm, vault configurations, SSH keys, and cryptocurrency wallets. The malware hides behind an eBPF kernel rootkit and communicates with its operator over the Tor network. It self-propagates by using stolen npm publishing credentials, including those linked to npm's Trusted Publishing workflow, to publish trojanized package versions. The attack originated from a compromised account named 'asteroiddao' and uses backdated Git commits to evade detection. It also leverages GitHub Actions for secret exfiltration, although this mechanism was not observed in the current attack. Early detection by security firms limited its spread. Remediation involves upgrading affected packages, rotating credentials, and enabling two-factor authentication.
Potential Impact
The malware compromises developer and CI environments by stealing a wide range of sensitive credentials and environment variables, potentially exposing cloud service keys, cryptographic keys, and cryptocurrency wallets. This enables the attacker to publish malicious package versions that further propagate the infection within the npm ecosystem. The attack could lead to widespread credential theft and compromise of development pipelines. However, the attack was detected early and did not spread to highly popular packages, limiting its impact.
Mitigation Recommendations
Security researchers recommend upgrading to fixed versions of the affected npm packages. Developers should rotate all potentially compromised keys and credentials. Enabling two-factor authentication (2FA) on all npm accounts is advised to prevent unauthorized publishing. Since this is a supply-chain attack, verifying package integrity before use is important. No official patch or vendor advisory is provided in the input; therefore, patch status is not yet confirmed — check vendor advisories for updates.
New IronWorm malware hits 36 packages in npm supply-chain attack
Description
A new supply-chain attack has infected 36 packages on the Node Package Manager (npm) index with infostealer malware called IronWorm. [...]
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
IronWorm is a Rust-based infostealer malware involved in a supply-chain attack targeting 36 packages on the npm registry. It steals sensitive environment variables and credential files including those for OpenAI, AWS, Anthropic, npm, vault configurations, SSH keys, and cryptocurrency wallets. The malware hides behind an eBPF kernel rootkit and communicates with its operator over the Tor network. It self-propagates by using stolen npm publishing credentials, including those linked to npm's Trusted Publishing workflow, to publish trojanized package versions. The attack originated from a compromised account named 'asteroiddao' and uses backdated Git commits to evade detection. It also leverages GitHub Actions for secret exfiltration, although this mechanism was not observed in the current attack. Early detection by security firms limited its spread. Remediation involves upgrading affected packages, rotating credentials, and enabling two-factor authentication.
Potential Impact
The malware compromises developer and CI environments by stealing a wide range of sensitive credentials and environment variables, potentially exposing cloud service keys, cryptographic keys, and cryptocurrency wallets. This enables the attacker to publish malicious package versions that further propagate the infection within the npm ecosystem. The attack could lead to widespread credential theft and compromise of development pipelines. However, the attack was detected early and did not spread to highly popular packages, limiting its impact.
Mitigation Recommendations
Security researchers recommend upgrading to fixed versions of the affected npm packages. Developers should rotate all potentially compromised keys and credentials. Enabling two-factor authentication (2FA) on all npm accounts is advised to prevent unauthorized publishing. Since this is a supply-chain attack, verifying package integrity before use is important. No official patch or vendor advisory is provided in the input; therefore, patch status is not yet confirmed — check vendor advisories for updates.
Technical Details
- Article Source
- {"url":"https://www.bleepingcomputer.com/news/security/new-ironworm-malware-hits-36-packages-in-npm-supply-chain-attack/","fetched":true,"fetchedAt":"2026-06-04T15:33:35.100Z","wordCount":816}
Threat ID: 6a219acfe29bf47b50b303db
Added to database: 6/4/2026, 3:33:35 PM
Last enriched: 6/4/2026, 3:33:40 PM
Last updated: 6/5/2026, 5:04:04 AM
Views: 20
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.