Malicious code in node-env-resolver-nextjs (npm)
The node-env-resolver-nextjs package version 7.4.2 on npm contains malicious code identified as the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files during package installation, bypassing security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or committing backdoor files to GitHub repositories.
AI Analysis
Technical Summary
The node-env-resolver-nextjs npm package version 7.4.2 was found to contain malicious code known as Miasma malware. This malware leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools focused on lifecycle scripts. Once executed, it attempts credential and OIDC token theft from various cloud and registry services. It further propagates by compromising additional packages managed by stolen accounts or by injecting backdoor files into GitHub repositories, enabling widespread infection and persistence.
Potential Impact
The malware can lead to credential and token theft for cloud and registry services, potentially allowing unauthorized access to sensitive environments. It also enables propagation across the npm ecosystem and GitHub repositories, increasing the risk of widespread compromise and persistent backdoors in software supply chains.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using node-env-resolver-nextjs version 7.4.2. Monitor vendor advisories for updates. Since this is a malicious package, removing the affected version and replacing it with a trusted alternative or a clean version when available is recommended.
Malicious code in node-env-resolver-nextjs (npm)
Description
The node-env-resolver-nextjs package version 7.4.2 on npm contains malicious code identified as the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files during package installation, bypassing security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or committing backdoor files to GitHub repositories.
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 node-env-resolver-nextjs npm package version 7.4.2 was found to contain malicious code known as Miasma malware. This malware leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools focused on lifecycle scripts. Once executed, it attempts credential and OIDC token theft from various cloud and registry services. It further propagates by compromising additional packages managed by stolen accounts or by injecting backdoor files into GitHub repositories, enabling widespread infection and persistence.
Potential Impact
The malware can lead to credential and token theft for cloud and registry services, potentially allowing unauthorized access to sensitive environments. It also enables propagation across the npm ecosystem and GitHub repositories, increasing the risk of widespread compromise and persistent backdoors in software supply chains.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using node-env-resolver-nextjs version 7.4.2. Monitor vendor advisories for updates. Since this is a malicious package, removing the affected version and replacing it with a trusted alternative or a clean version when available is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5265
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6768715ace4315a408
Added to database: 07/09/2026, 09:39:51 UTC
Last enriched: 07/09/2026, 10:05:07 UTC
Last updated: 07/27/2026, 07:25:08 UTC
Views: 31
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.