Which versions of npm-rce-poc are malicious?

The following npm versions of npm-rce-poc are flagged malicious: 1.0.13. Treat any of these as compromised.

How do I remediate npm-rce-poc if I installed it?

npm-rce-poc is a typosquat — you almost certainly intended a legitimately-named package. Remove npm-rce-poc, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed npm-rce-poc — how do I know if it already compromised me?

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

Yes — npm-rce-poc is associated with the IN-MAL-2026-008249 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 npm-rce-poc 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 npm-rce-poc (version 1.0.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-rce-poc across your stack and pipelines.

Malicious package

npm-rce-pocnpm

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

MAL-2026-7019

Immediate action

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

npm uninstall npm-rce-poc

What this malware does

Package declares a postinstall lifecycle script that, on npm install, fetches a script over plain HTTP from a hardcoded bare IP (http://115.190.124.243:8761/slt on Unix,.../swt on Windows) and immediately executes it — piping to sh on Unix and writing to C:\Users\Public\run.bat via certutil then invoking it on Windows. The package presents itself as date-fns-lite, a lookalike of the popular date-fns library, and ships a benign-looking date-formatting index.js as cover; the actual behavior is an install-time dropper that hands remote code execution to the operator of 115.190.124.243 against every installer. No pinning, no integrity check, no TLS.

Malicious versions

1 flagged

1.0.13

Indicators of compromise (SHA-256)

6365312ad1339c7d5539f594b9e472ea3f10401fa356fe49766de887368e87c9

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npm-rce-poc (version 1.0.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-rce-poc across your stack and pipelines.
If you installed it — respond
npm-rce-poc is a typosquat — you almost certainly intended a legitimately-named package. Remove npm-rce-poc, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If npm-rce-poc 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 npm-rce-poc 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. npm-rce-poc on npm has been identified as a malicious package (version 1.0.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008249

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks npm-rce-poc-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