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

o0o9npm

o0o9 is a confirmed malicious npm package (MAL-2026-14277) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in o0o9 (npm)

MAL-2026-14277
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall o0o9

What this malware does

The package's main entry index.js imports child_process at the top of the file and invokes spawn("powershell",...) as a top-level side effect (line 27). Loading the module via require/import causes an unprompted PowerShell process to launch on the installer's machine, which is a Windows-focused code execution vector wholly unrelated to any legitimate library function. This is the shape of an install/import-time execution payload rather than an API a caller must opt into.

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

18 flagged
1.0.01.0.11.0.21.0.31.0.41.0.61.0.71.0.81.0.91.1.11.2.11.3.01.4.01.8.01.8.12.0.02.0.12.0.2

Indicators of compromise (SHA-256)

a1d425848ef7172faf5f84ff9bd9017bf3ab1eb2343a5301ff0df1711d091118
dc07d1bcb92034037f41bf30cf6bd67f5313276df6aeef3a805d4b52d757e22b
cfa80ca978039496a1bbb61c58e36f8ce05b3fd4df7d6251b1b90e9706164ce8
b5b99531109b7927c15c3f20ae70c2a8e473e7cb9387410baf0bf78bcf4f810a
f7fb3e741dcf3b5520731af0a67aa71ff7f78c910f5d08a9805db60095aeb4e3
290655c6cd5d5efa6c9dfd2c391cdb4fed9678b2945ae4f2ec9524f4e95d7c02
5d501804e6b82d829ddeecdf524795fb7a45fce6684fe92adc35dbfb14058c4a
bb45c07e4348e54eefc3bdd3891d08dc378e7e32ecd3e0f885204261d155610e
ea2ce18356819a4f712493c249282501fc0eaab9deba0e76da810f0ed467dd58
1f84015eef7a1a5ee86e03beea80ed75a7c88c8d30cd6b24661eeee6c61ed508
258d86a8a3ab912648075c3677ef18ef578d12ecf427892bf6b91b5a23706fd7
354e0f76003049ad78597d5bde7464c3f4b72663ea2045988f56aa5ca9f0c894
74f8c5d5b5e0d413c0e7b2021498fec1535db865b6a0ff089328628464bf3cf1
fc4830b67edad81a1789c3aba24e265d22fbae22d241088a0aa249b7648ca94e
062c9570af2681819a748bcde555a75fa8bae5ead93a9837b4f3a45d16a3228b
493e501736a7f045990690e0b11ab9a5a056d974ca61c80b8eaafb50df88d0d4
65f15b6d39bb6626944cb9383b297cf61f878ab2f7aa6650a178c6154496721e
834f8d2d203f9b0ef36ebce8e360a50aebd2953e29756bef4c4d203c6394192b
ad40a56d23d35bfb26c6e546357a6c45db50f26e497976ddfb641ee041718c21

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for o0o9 (18 malicious versions).

  2. If you installed it — respond

    Remove o0o9 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 o0o9 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. o0o9 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.6, 1.0.7, 1.0.8, and 10 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018390IN-MAL-2026-018389GHSA-5f5h-pg84-39h4IN-MAL-2026-020734IN-MAL-2026-020733IN-MAL-2026-020730IN-MAL-2026-020723IN-MAL-2026-020732IN-MAL-2026-020724IN-MAL-2026-020729IN-MAL-2026-020727IN-MAL-2026-020735IN-MAL-2026-020736IN-MAL-2026-020728IN-MAL-2026-020725IN-MAL-2026-020737IN-MAL-2026-020726IN-MAL-2026-020731IN-MAL-2026-020722

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks o0o9-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

o0o9 (npm) malicious package — MAL-2026-14277 | O3 Security