Which versions of cms_comp_static are malicious?

The following npm versions of cms_comp_static are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate cms_comp_static if I installed it?

Remove cms_comp_static 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 cms_comp_static — how do I know if it already compromised me?

If cms_comp_static 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 cms_comp_static part of a known attack campaign?

Yes — cms_comp_static is associated with the GHSA-7r25-49qj-j573, RLMA-2026-01210 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 cms_comp_static 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 cms_comp_static (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cms_comp_static across your stack and pipelines.

Malicious package

cms_comp_staticnpm

Malicious code in cms_comp_static (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192556

Immediate action

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

npm uninstall cms_comp_static

What this malware does

The package cms_comp_static 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.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

38ce02191cf2d82246d56083ba8f7c2c4c0f14a71060bf8beaea95851f3c7a1e

4e057568833f54e2250c5364e595d7a3046f4eb94f2484b9a0a2236b948cb10f

7b77118c3854008adbc2124acf4b275a83e17f9a78efae6893c71aa51827829a

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 cms_comp_static (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cms_comp_static across your stack and pipelines.
If you installed it — respond
Remove cms_comp_static 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 cms_comp_static 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 cms_comp_static 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. cms_comp_static on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7r25-49qj-j573RLMA-2026-01210

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cms_comp_static-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