Which versions of demo-ip-package-cm are malicious?

The following npm versions of demo-ip-package-cm are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate demo-ip-package-cm if I installed it?

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

If demo-ip-package-cm 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 demo-ip-package-cm part of a known attack campaign?

Yes — demo-ip-package-cm is associated with the GHSA-qcqp-vg8x-vrq6, RLMA-2026-01240, RLUA-2026-01740 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 demo-ip-package-cm 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 demo-ip-package-cm (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging demo-ip-package-cm across your stack and pipelines.

Malicious package

demo-ip-package-cmnpm

Malicious code in demo-ip-package-cm (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1197

Immediate action

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

npm uninstall demo-ip-package-cm

What this malware does

The package demo-ip-package-cm 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

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

a1c01b1af796859f5b27fa87dab78284436476673974a47157c10102d7a973d4

756fbc97ea8b65830898805513bede65c955e6ae300a4d19574e984d17615b37

edb05bfdadb82de9669f953a735b0fef63c6f50ad22d950ffa54f84b847449d2

ce24c9d52bd95bb2fd2d68d4f3b4ad71396a29f08d874ff10e5e68510fef952e

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

Campaign

GHSA-qcqp-vg8x-vrq6RLMA-2026-01240RLUA-2026-01740

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks demo-ip-package-cm-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