Malicious code in github-archiver (npm)
The github-archiver npm package versions 1.0.0 through 1.5.7 contain malicious code known as the Miasma malware. This malware executes during package installation by abusing weaponized binding.gyp files, bypassing typical security inspections. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or injecting backdoors into GitHub repositories. Systems with this package installed should be considered fully compromised, and all secrets should be rotated from a different machine.
AI Analysis
Technical Summary
The github-archiver npm package contains malicious code identified as Miasma malware, which executes during installation by exploiting binding.gyp files to evade lifecycle script inspections. Once executed, it exfiltrates credentials and OIDC tokens for various cloud and registry services. The malware propagates by compromising other npm packages managed by stolen accounts or by committing backdoor files to GitHub repositories. Any system with this package installed is considered fully compromised, necessitating immediate secret rotation and package removal. However, removal alone may not eliminate all malicious artifacts due to potential full system compromise.
Potential Impact
Systems with the affected versions of github-archiver installed are fully compromised. The malware can steal sensitive credentials and tokens, enabling unauthorized access to cloud and registry services. It also self-propagates by compromising other packages and repositories, increasing the attack surface and persistence. This can lead to widespread credential theft, unauthorized code injection, and potential long-term compromise of development environments.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. Immediate removal of the github-archiver package from affected systems is required. All secrets, keys, and tokens stored on compromised machines must be rotated from a secure, unaffected device. Due to the potential full compromise of the system, consider rebuilding or thoroughly cleaning affected environments. Monitor for any signs of persistence or backdoors introduced by the malware. Check vendor advisories and npm security resources for any updates or remediation guidance.
Malicious code in github-archiver (npm)
Description
The github-archiver npm package versions 1.0.0 through 1.5.7 contain malicious code known as the Miasma malware. This malware executes during package installation by abusing weaponized binding.gyp files, bypassing typical security inspections. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or injecting backdoors into GitHub repositories. Systems with this package installed should be considered fully compromised, and all secrets should be rotated from a different machine.
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 github-archiver npm package contains malicious code identified as Miasma malware, which executes during installation by exploiting binding.gyp files to evade lifecycle script inspections. Once executed, it exfiltrates credentials and OIDC tokens for various cloud and registry services. The malware propagates by compromising other npm packages managed by stolen accounts or by committing backdoor files to GitHub repositories. Any system with this package installed is considered fully compromised, necessitating immediate secret rotation and package removal. However, removal alone may not eliminate all malicious artifacts due to potential full system compromise.
Potential Impact
Systems with the affected versions of github-archiver installed are fully compromised. The malware can steal sensitive credentials and tokens, enabling unauthorized access to cloud and registry services. It also self-propagates by compromising other packages and repositories, increasing the attack surface and persistence. This can lead to widespread credential theft, unauthorized code injection, and potential long-term compromise of development environments.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. Immediate removal of the github-archiver package from affected systems is required. All secrets, keys, and tokens stored on compromised machines must be rotated from a secure, unaffected device. Due to the potential full compromise of the system, consider rebuilding or thoroughly cleaning affected environments. Monitor for any signs of persistence or backdoors introduced by the malware. Check vendor advisories and npm security resources for any updates or remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5259
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-r6pp-cq9f-9j94"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6c68715ace4315a8cf
Added to database: 07/09/2026, 09:39:56 UTC
Last enriched: 07/09/2026, 10:06:09 UTC
Last updated: 07/27/2026, 06:44:36 UTC
Views: 8
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.