Malicious code in mountly (npm)
The npm package 'mountly' version 0.2.2 contains malicious code associated with the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files to execute code during package installation, bypassing security tools that only inspect lifecycle scripts. Upon execution, 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 'mountly' npm package version 0.2.2 was found to contain malicious code or a dependency with malicious code linked to the Miasma malware. Miasma is a self-propagating worm that leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools that focus on lifecycle scripts. The malware's payload includes exfiltration of credentials and OIDC tokens for various cloud and registry services. It further propagates by compromising other npm packages managed by the stolen accounts or by committing backdoor files to GitHub repositories, facilitating widespread infection within the npm ecosystem.
Potential Impact
The malicious code in mountly 0.2.2 can lead to credential and token theft for cloud and registry services, potentially allowing attackers to gain unauthorized access to these services. The malware can propagate by compromising additional packages or repositories, increasing the scope of infection and risk within the npm ecosystem and associated development environments.
Mitigation Recommendations
No official patch or remediation is currently documented for mountly 0.2.2. Users should avoid using this version of the package. It is recommended to audit dependencies for malicious code and monitor for suspicious activity related to credential exfiltration. Check vendor advisories or npm security advisories for updates or fixes. Since this is not a cloud service, remediation depends on users removing or replacing the affected package version.
Malicious code in mountly (npm)
Description
The npm package 'mountly' version 0.2.2 contains malicious code associated with the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files to execute code during package installation, bypassing security tools that only inspect lifecycle scripts. Upon execution, 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 'mountly' npm package version 0.2.2 was found to contain malicious code or a dependency with malicious code linked to the Miasma malware. Miasma is a self-propagating worm that leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools that focus on lifecycle scripts. The malware's payload includes exfiltration of credentials and OIDC tokens for various cloud and registry services. It further propagates by compromising other npm packages managed by the stolen accounts or by committing backdoor files to GitHub repositories, facilitating widespread infection within the npm ecosystem.
Potential Impact
The malicious code in mountly 0.2.2 can lead to credential and token theft for cloud and registry services, potentially allowing attackers to gain unauthorized access to these services. The malware can propagate by compromising additional packages or repositories, increasing the scope of infection and risk within the npm ecosystem and associated development environments.
Mitigation Recommendations
No official patch or remediation is currently documented for mountly 0.2.2. Users should avoid using this version of the package. It is recommended to audit dependencies for malicious code and monitor for suspicious activity related to credential exfiltration. Check vendor advisories or npm security advisories for updates or fixes. Since this is not a cloud service, remediation depends on users removing or replacing the affected package version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5260
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6768715ace4315a41b
Added to database: 07/09/2026, 09:39:51 UTC
Last enriched: 07/09/2026, 10:05:34 UTC
Last updated: 07/20/2026, 13:02:02 UTC
Views: 7
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.