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

rce-poc-test-honor-devnpm

rce-poc-test-honor-dev is a confirmed malicious npm package (MAL-2025-49382) that executes malicious code on install (malicious versions 1.0.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rce-poc-test-honor-dev (npm)

MAL-2025-49382
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rce-poc-test-honor-dev

What this malware does

The package rce-poc-test-honor-dev 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.02.0.0

Indicators of compromise (SHA-256)

7579108bcec121c6cdb61d1ead8cd23f32c2d808b817b87f6fe371427180a0f9
b66eed52fc0c24b51f24da6c244c23fc29ce6228dd4a97a0606f71bb254f02b7
dfcc9e684fc41822187e74ab25f70748d41101443ffdb837c012b3241bcfb717
e94a0d1446851d8594605c59ea3e989f8acaa918a16aedf93007b0ca8a5d67e5

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 rce-poc-test-honor-dev (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rce-poc-test-honor-dev across your stack and pipelines.

  2. If you installed it — respond

    Remove rce-poc-test-honor-dev 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 rce-poc-test-honor-dev 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 rce-poc-test-honor-dev 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. rce-poc-test-honor-dev on npm has been identified as a malicious package (versions 1.0.0, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4gpw-28rw-46xpRLMA-2025-05922RLUA-2025-06453

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks rce-poc-test-honor-dev-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.

Explore

rce-poc-test-honor-dev (npm) malicious package — MAL-2025-49382 | O3 Security