Which versions of npm-rce-safe-proof-yourname are malicious?

The following npm versions of npm-rce-safe-proof-yourname are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate npm-rce-safe-proof-yourname if I installed it?

npm-rce-safe-proof-yourname is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed npm-rce-safe-proof-yourname — how do I know if it already compromised me?

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

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

Malicious package

npm-rce-safe-proof-yournamenpm

npm-rce-safe-proof-yourname is a confirmed malicious npm package (MAL-2026-10159) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npm-rce-safe-proof-yourname (npm)

MAL-2026-10159

Immediate action

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

npm uninstall npm-rce-safe-proof-yourname

What this malware does

On npm install, postinstall.js runs whoami, reads os.hostname(), process.platform, and process.version, and transmits them via HTTPS GET to a hardcoded remote endpoint at https://testnpm.byte.eyes.sh/npm-proof. This fires automatically as a lifecycle hook with no user consent. The package's declared purpose (npm script for showing date strings) and its self-labeling as a 'safe proof' do not match the observed behavior — the code is a functional install-time identity beacon transmitting the installer's username and hostname to an author-controlled destination. Beaconing installer identity to a hardcoded third-party host on install is credential/identity leakage regardless of the 'proof' framing.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f9fdedc15d959d978bd3563d29d16c5ab226d3c4fa4ab8b6fecf8bdf130e29ab

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npm-rce-safe-proof-yourname (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-rce-safe-proof-yourname across your stack and pipelines.
If you installed it — respond
npm-rce-safe-proof-yourname is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If npm-rce-safe-proof-yourname 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-safe-proof-yourname 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-safe-proof-yourname on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009647

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks npm-rce-safe-proof-yourname-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database