Malicious code in executable-stories-vitest (npm)
The executable-stories-vitest npm package versions 2.0.1, 3.1.1, 4.0.1, 5.0.1, 6.1.1, 7.0.3, and 8.3.3 have been identified as containing malicious code associated with the Miasma malware. This malware propagates by abusing binding.gyp files to execute code during package installation, bypassing typical security inspections. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and spreads by compromising other packages and repositories. No direct installer harm or lifecycle script behavior was confirmed in these versions, but the malware's propagation and credential theft capabilities pose significant risk.
AI Analysis
Technical Summary
The malicious code in the executable-stories-vitest npm package is linked to the Miasma malware, a self-propagating worm that exploits weaponized binding.gyp files to execute during package installation. This technique bypasses security tools that only inspect lifecycle scripts. Once executed, the malware attempts to steal credentials and OIDC tokens for cloud and registry services and propagates by compromising additional packages and GitHub repositories. Automated analysis did not detect direct installer harm or typical malicious lifecycle script behavior, but the malware's stealthy execution and credential exfiltration capabilities necessitate human review and caution.
Potential Impact
The malware can exfiltrate sensitive credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It can also propagate by compromising other npm packages and GitHub repositories, increasing the scope of infection and risk to supply chain integrity. Although no direct installer harm or network beaconing was confirmed, the credential theft and propagation mechanisms present a significant threat to affected environments.
Mitigation Recommendations
No official patch or remediation is currently documented for these affected versions. Users should avoid using the specified versions of executable-stories-vitest (2.0.1, 3.1.1, 4.0.1, 5.0.1, 6.1.1, 7.0.3, 8.3.3) until further guidance or fixes are provided. Conduct manual review of package dependencies and consider removing or replacing this package. Monitor for updates from the package maintainers or security advisories for official fixes. Since this is not a cloud service, remediation depends on user action.
Malicious code in executable-stories-vitest (npm)
Description
The executable-stories-vitest npm package versions 2.0.1, 3.1.1, 4.0.1, 5.0.1, 6.1.1, 7.0.3, and 8.3.3 have been identified as containing malicious code associated with the Miasma malware. This malware propagates by abusing binding.gyp files to execute code during package installation, bypassing typical security inspections. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and spreads by compromising other packages and repositories. No direct installer harm or lifecycle script behavior was confirmed in these versions, but the malware's propagation and credential theft capabilities pose significant risk.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The malicious code in the executable-stories-vitest npm package is linked to the Miasma malware, a self-propagating worm that exploits weaponized binding.gyp files to execute during package installation. This technique bypasses security tools that only inspect lifecycle scripts. Once executed, the malware attempts to steal credentials and OIDC tokens for cloud and registry services and propagates by compromising additional packages and GitHub repositories. Automated analysis did not detect direct installer harm or typical malicious lifecycle script behavior, but the malware's stealthy execution and credential exfiltration capabilities necessitate human review and caution.
Potential Impact
The malware can exfiltrate sensitive credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It can also propagate by compromising other npm packages and GitHub repositories, increasing the scope of infection and risk to supply chain integrity. Although no direct installer harm or network beaconing was confirmed, the credential theft and propagation mechanisms present a significant threat to affected environments.
Mitigation Recommendations
No official patch or remediation is currently documented for these affected versions. Users should avoid using the specified versions of executable-stories-vitest (2.0.1, 3.1.1, 4.0.1, 5.0.1, 6.1.1, 7.0.3, 8.3.3) until further guidance or fixes are provided. Conduct manual review of package dependencies and consider removing or replacing this package. Monitor for updates from the package maintainers or security advisories for official fixes. Since this is not a cloud service, remediation depends on user action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5258
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6c68715ace4315a8d8
Added to database: 07/09/2026, 09:39:56 UTC
Last enriched: 07/09/2026, 10:06:17 UTC
Last updated: 07/25/2026, 23:46:04 UTC
Views: 12
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.
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.