Malicious code in autotel-backends (npm)
The autotel-backends npm package version 2.12.26 contains malicious code known as the Miasma malware. This malware is a self-propagating worm that exploits weaponized 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 or repositories. Any system with this package installed should be considered fully compromised, and secrets must be rotated immediately. Removing the package alone may not eliminate all malicious components.
AI Analysis
Technical Summary
The autotel-backends package version 2.12.26 is identified as containing malicious code linked to the Miasma malware. This malware propagates through the npm registry by abusing binding.gyp files to execute during installation, evading detection by security tools that focus on lifecycle scripts. It exfiltrates credentials and OIDC tokens for cloud and registry services and spreads by compromising additional packages or injecting backdoors into GitHub repositories. Systems with this package installed are at high risk of full compromise.
Potential Impact
Systems with autotel-backends version 2.12.26 installed are considered fully compromised. The malware can exfiltrate sensitive credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It also propagates by compromising other packages and repositories, increasing the scope of infection. Removing the package does not guarantee full remediation due to possible persistent backdoors or additional malware installed.
Mitigation Recommendations
Immediate removal of the autotel-backends package version 2.12.26 is required. All secrets and keys stored on the compromised system should be rotated immediately from a different, trusted system. Because the malware may have established persistent control, further forensic analysis and system remediation are recommended. Patch status is not confirmed; check vendor advisories for updates or official fixes.
Malicious code in autotel-backends (npm)
Description
The autotel-backends npm package version 2.12.26 contains malicious code known as the Miasma malware. This malware is a self-propagating worm that exploits weaponized 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 or repositories. Any system with this package installed should be considered fully compromised, and secrets must be rotated immediately. Removing the package alone may not eliminate all malicious components.
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 autotel-backends package version 2.12.26 is identified as containing malicious code linked to the Miasma malware. This malware propagates through the npm registry by abusing binding.gyp files to execute during installation, evading detection by security tools that focus on lifecycle scripts. It exfiltrates credentials and OIDC tokens for cloud and registry services and spreads by compromising additional packages or injecting backdoors into GitHub repositories. Systems with this package installed are at high risk of full compromise.
Potential Impact
Systems with autotel-backends version 2.12.26 installed are considered fully compromised. The malware can exfiltrate sensitive credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It also propagates by compromising other packages and repositories, increasing the scope of infection. Removing the package does not guarantee full remediation due to possible persistent backdoors or additional malware installed.
Mitigation Recommendations
Immediate removal of the autotel-backends package version 2.12.26 is required. All secrets and keys stored on the compromised system should be rotated immediately from a different, trusted system. Because the malware may have established persistent control, further forensic analysis and system remediation are recommended. Patch status is not confirmed; check vendor advisories for updates or official fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5215
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-9p9m-f2hg-9gxm"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed2927e9c79719934b11
Added to database: 06/29/2026, 22:09:45 UTC
Last enriched: 07/09/2026, 10:50:37 UTC
Last updated: 07/30/2026, 04:15:00 UTC
Views: 15
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.