MAL-2026-5221: Malicious code in autotel-eventcatalog (npm)
The autotel-eventcatalog npm package versions 1.0.1, 2.0.1, 3.0.1, 4.0.2, and 5.0.1 contain malicious code known as the Miasma malware. This malware propagates by abusing 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 and repositories. Any system with this package installed should be considered fully compromised.
AI Analysis
Technical Summary
The autotel-eventcatalog npm package is affected by a malicious code infection identified as Miasma malware. This malware uses weaponized binding.gyp files to execute during installation, evading detection by security tools that only inspect lifecycle scripts. It exfiltrates sensitive credentials and tokens and propagates by compromising additional packages and GitHub repositories. The affected versions are 1.0.1, 2.0.1, 3.0.1, 4.0.2, and 5.0.1. There is no evidence of installer-harm or lifecycle-script droppers in the analyzed signals, but the malware's self-propagating nature and credential theft capabilities make it highly dangerous.
Potential Impact
Systems with any of the affected autotel-eventcatalog package versions installed are considered fully compromised. The malware can exfiltrate credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It also propagates by compromising other packages and repositories, increasing the attack surface and risk of further compromise.
Mitigation Recommendations
Remove the affected autotel-eventcatalog package versions immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted computer. Due to the potential for full system compromise, assume that removing the package alone may not eliminate all malicious components. Conduct a thorough investigation and remediation of the affected systems. No official patch or fix is currently indicated; monitor vendor advisories for updates.
MAL-2026-5221: Malicious code in autotel-eventcatalog (npm)
Description
The autotel-eventcatalog npm package versions 1.0.1, 2.0.1, 3.0.1, 4.0.2, and 5.0.1 contain malicious code known as the Miasma malware. This malware propagates by abusing 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 and repositories. Any system with this package installed should be considered fully compromised.
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-eventcatalog npm package is affected by a malicious code infection identified as Miasma malware. This malware uses weaponized binding.gyp files to execute during installation, evading detection by security tools that only inspect lifecycle scripts. It exfiltrates sensitive credentials and tokens and propagates by compromising additional packages and GitHub repositories. The affected versions are 1.0.1, 2.0.1, 3.0.1, 4.0.2, and 5.0.1. There is no evidence of installer-harm or lifecycle-script droppers in the analyzed signals, but the malware's self-propagating nature and credential theft capabilities make it highly dangerous.
Potential Impact
Systems with any of the affected autotel-eventcatalog package versions installed are considered fully compromised. The malware can exfiltrate credentials and tokens, potentially leading to unauthorized access to cloud and registry services. It also propagates by compromising other packages and repositories, increasing the attack surface and risk of further compromise.
Mitigation Recommendations
Remove the affected autotel-eventcatalog package versions immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted computer. Due to the potential for full system compromise, assume that removing the package alone may not eliminate all malicious components. Conduct a thorough investigation and remediation of the affected systems. No official patch or fix is currently indicated; monitor vendor advisories for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5221
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-h58c-49hq-mq6c"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7768715ace4315ad5b
Added to database: 07/09/2026, 09:40:07 UTC
Last enriched: 07/09/2026, 10:09:38 UTC
Last updated: 07/09/2026, 17:47:19 UTC
Views: 9
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.