MAL-2026-5203: Malicious code in @ethlete/theming (npm)
The npm package @ethlete/theming version 2.7.1 contains malicious code identified as 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. 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 @ethlete/theming npm package at version 2.7.1 was found to contain malicious code linked to the Miasma malware. Miasma is a self-propagating worm that spreads within the npm ecosystem by exploiting binding.gyp files to execute malicious code during package installation, circumventing 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, enabling further compromise. It propagates by taking over other packages managed by stolen accounts or by injecting backdoor files into GitHub repositories, facilitating widespread infection.
Potential Impact
This malicious package can lead to credential theft, including cloud and registry service tokens, potentially allowing attackers to compromise additional packages and repositories. This can result in supply chain attacks affecting downstream users who install or update the compromised package version.
Mitigation Recommendations
No official patch or remediation guidance is provided for this package version. Users should avoid using @ethlete/theming version 2.7.1 and remove it from their projects if present. Monitor for updates or advisories from the package maintainers or npm registry. Consider auditing dependencies for malicious code and rotating any potentially exposed credentials or tokens.
MAL-2026-5203: Malicious code in @ethlete/theming (npm)
Description
The npm package @ethlete/theming version 2.7.1 contains malicious code identified as 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. 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 @ethlete/theming npm package at version 2.7.1 was found to contain malicious code linked to the Miasma malware. Miasma is a self-propagating worm that spreads within the npm ecosystem by exploiting binding.gyp files to execute malicious code during package installation, circumventing 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, enabling further compromise. It propagates by taking over other packages managed by stolen accounts or by injecting backdoor files into GitHub repositories, facilitating widespread infection.
Potential Impact
This malicious package can lead to credential theft, including cloud and registry service tokens, potentially allowing attackers to compromise additional packages and repositories. This can result in supply chain attacks affecting downstream users who install or update the compromised package version.
Mitigation Recommendations
No official patch or remediation guidance is provided for this package version. Users should avoid using @ethlete/theming version 2.7.1 and remove it from their projects if present. Monitor for updates or advisories from the package maintainers or npm registry. Consider auditing dependencies for malicious code and rotating any potentially exposed credentials or tokens.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5203
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7768715ace4315ad4d
Added to database: 07/09/2026, 09:40:07 UTC
Last enriched: 07/09/2026, 10:09:21 UTC
Last updated: 07/09/2026, 10:35:30 UTC
Views: 3
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.