Which versions of roots-cms-client are malicious?

The following npm versions of roots-cms-client are flagged malicious: 0.0.99. Treat any of these as compromised.

How do I remediate roots-cms-client if I installed it?

Remove roots-cms-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed roots-cms-client — how do I know if it already compromised me?

If roots-cms-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is roots-cms-client part of a known attack campaign?

Yes — roots-cms-client is associated with the GHSA-q57g-x3rh-xj4x campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find roots-cms-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for roots-cms-client (version 0.0.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging roots-cms-client across your stack and pipelines.

Malicious package

roots-cms-clientnpm

Malicious code in roots-cms-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-617

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall roots-cms-client

What this malware does

The package roots-cms-client was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'roots-cms-client' @ 0.0.99 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.99

Indicators of compromise (SHA-256)

5290f63f945a36e1d28eaf7c6340896e82a974ec0971f8bee7a52dfda4fc3e68

9670a58bdf8573b9c7d94a74cf58593a55692bfcf33d931693680389b981f89c

88007d193d64ac8d7a2a970903353601b1f620a48f22c3cd3c7a838da0cce4e8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for roots-cms-client (version 0.0.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging roots-cms-client across your stack and pipelines.
If you installed it — respond
Remove roots-cms-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If roots-cms-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks roots-cms-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. roots-cms-client on npm has been identified as a malicious package (version 0.0.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q57g-x3rh-xj4x

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks roots-cms-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring