Which versions of demo-ip-package are malicious?

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

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

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

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

Yes — demo-ip-package is associated with the GHSA-f9r2-36vp-352g, RLMA-2026-01239, RLUA-2026-01739 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 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 (3 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 across your stack and pipelines.

Malicious package

demo-ip-packagenpm

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

MAL-2026-1196

Immediate action

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

npm uninstall demo-ip-package

What this malware does

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

3 flagged

1.0.01.0.11.0.5

Indicators of compromise (SHA-256)

9377708b245cac5b751ac6dc75d9218b993bcb4cebed6f2049a542868f5df316

94f9378de5524843952c850c47aae7cc5373145c2b41032b764da720e9a0656f

7e8dca2c851fef446b1f1e41f8f4712f4d449f9601904d67d9d40431090ab2cb

b3ec9e0d179f2d9fa6cceffbf3b9f0d17cda45e50c972c9146f35d09c4acdbd4

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 (3 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 across your stack and pipelines.
If you installed it — respond
Remove demo-ip-package 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 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 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 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f9r2-36vp-352gRLMA-2026-01239RLUA-2026-01739

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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