Which versions of cms-storehub are malicious?

The following npm versions of cms-storehub are flagged malicious: 1.3.6. Treat any of these as compromised.

How do I remediate cms-storehub if I installed it?

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

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

Yes — cms-storehub is associated with the GHSA-gvmr-7vwj-2mmf 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-storehub 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-storehub (version 1.3.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cms-storehub across your stack and pipelines.

Malicious package

cms-storehubnpm

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

MAL-2026-5097

Immediate action

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

npm uninstall cms-storehub

What this malware does

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 'cms-storehub' @ 1.3.6 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.3.6

Indicators of compromise (SHA-256)

70597dd32a309375aebdec2fda84aa2ea8cd1a755254181436f1b41a512783f6

dda5fa0b4771a3299568c8dd8d17d5663d9c8ae782b8c71f4a2baf0ce1f8e5ee

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

Campaign

GHSA-gvmr-7vwj-2mmf

References

github.com

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks cms-storehub-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