@forjacms/client (npm) · Malicious Code
Affects @forjacms/clientSource GCVE Database
Malicious package : remove @forjacms/client and rotate any secrets on hosts that installed it.
Data as of 9 Jul 2026, 10:09 UTC
Malicious package
Published to npm · OSV MAL-2026-5206
What to do
Remove @forjacms/client 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 |
|---|---|---|
| npm@forjacms/client | 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 npm package @forjacms/client versions 1.8.4 and 1.8.5 contain malicious code associated with the Miasma malware. This malware propagates 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 spreads by compromising other packages or committing backdoors to GitHub repositories.
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)
- npmjs.com/package/@forjacms/client/v/1.8.5 (opens in a new tab)
- npmjs.com/package/@forjacms/client/v/1.8.4 (opens in a new tab)