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

console-style-pro0o0o0onpm

Malicious code in console-style-pro0o0o0o (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-880
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall console-style-pro0o0o0o

What this malware does

The package console-style-pro0o0o0o 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

16384b6bafdd89d9d8daaceb69c33fbb0b9f923464599f6592657b6d1a5b684a
0fe7407a5523ef7efe6bec615d9601fe978b9e5de59d19d7e8e2ff054c5e09e9

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 console-style-pro0o0o0o (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging console-style-pro0o0o0o across your stack and pipelines.

  2. If you installed it — respond

    Remove console-style-pro0o0o0o 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 console-style-pro0o0o0o 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 console-style-pro0o0o0o 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. console-style-pro0o0o0o on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r4v3-x2p5-xc5v

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks console-style-pro0o0o0o-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.

console-style-pro0o0o0o (npm) malicious package — MAL-2026-880 | O3 Security