Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cms-cataloguenpm

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

MAL-2026-2011
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cms-catalogue

What this malware does

The package cms-catalogue was found to contain malicious code.

The OpenSSF Package Analysis project identified 'cms-catalogue' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
99.0.099.0.1

Indicators of compromise (SHA-256)

b1e5887ae48f20db99c60c5424798e9abab99d40af1c9f62074ea43ddbe9eb82
e2b6e877ee3e0be9b6fa0c5ca347f01ce90381e62e9c5ad293879cb0173b6742
d08a53064a76469a8b5ab4afdb3aa2907127f26f98ac8255e3ae650f8ce5d1ba

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove cms-catalogue 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.

  3. Did it already run?

    If cms-catalogue 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.

  4. How O3 protects you

    O3 blocks cms-catalogue 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-catalogue on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks cms-catalogue-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.

cms-catalogue (npm) malicious package — MAL-2026-2011 | O3 Security