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

oci-console-plugin-registrynpm

oci-console-plugin-registry is a confirmed malicious npm package (MAL-2025-47333) that executes malicious code on install (malicious version 2.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oci-console-plugin-registry (npm)

MAL-2025-47333
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall oci-console-plugin-registry

What this malware does

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

1 flagged
2.999.0

Indicators of compromise (SHA-256)

19ce011b024c9c3dcf78578cbf559de94a96364525ace53ce28457dba2053bf9
5961b7cd25f8ba51c2223c2e4cac1400971a03891f4ed851304ca9a1060909d4
1acd9c17aa0127114a6961fed4f9e23dc51acf24682665bd43e7fa73293605bf
eb77e8e9874d5f44c803b2173e7ab19dffc4bc47188101a5237f45d5fe96b9ef
b0ca4c8f2136074a674eb31c292a64657111a412633a76675f85f4845d8d9cfb

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 oci-console-plugin-registry (version 2.999.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oci-console-plugin-registry across your stack and pipelines.

  2. If you installed it — respond

    Remove oci-console-plugin-registry 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 oci-console-plugin-registry 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 oci-console-plugin-registry 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. oci-console-plugin-registry on npm has been identified as a malicious package (version 2.999.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mmxw-xxrr-4h5rRLMA-2025-05098RLUA-2026-01469

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks oci-console-plugin-registry-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

oci-console-plugin-registry (npm) malicious package — MAL-2025-47333 | O3 Security