github-archiver (npm) · Malicious Code
Affects github-archiverSource GCVE Database
Malicious package : remove github-archiver and rotate any secrets on hosts that installed it.
Data as of 9 Jul 2026, 10:06 UTC
Malicious package
Published to npm · OSV MAL-2026-5259
What to do
Remove github-archiver from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmgithub-archiver | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- endorlabs.com/learn/malicious-payload-in-ai-sdk-ollama-npm-package (opens in a new tab)
- stepsecurity.io/blog/binding-gyp-npm-supply-chain-attack-spreads-like-worm (opens in a new tab)
- github.com/advisories/GHSA-r6pp-cq9f-9j94 (opens in a new tab)
- npmjs.com/package/github-archiver/v/1.5.4 (opens in a new tab)
- npmjs.com/package/github-archiver/v/1.5.7 (opens in a new tab)
- npmjs.com/package/github-archiver/v/1.5.5 (opens in a new tab)
- npmjs.com/package/github-archiver/v/1.5.6 (opens in a new tab)