Which versions of aaaa89852889 are malicious?

The following npm versions of aaaa89852889 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate aaaa89852889 if I installed it?

Remove aaaa89852889 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.

I already installed aaaa89852889 — how do I know if it already compromised me?

If aaaa89852889 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 aaaa89852889 part of a known attack campaign?

Yes — aaaa89852889 is associated with the RLMA-2025-00047, RLUA-2026-10669 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 aaaa89852889 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 aaaa89852889 (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 aaaa89852889 across your stack and pipelines.

Malicious package

aaaa89852889npm

aaaa89852889 is a confirmed malicious npm package (MAL-2025-789) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aaaa89852889 (npm)

MAL-2025-789

Immediate action

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

npm uninstall aaaa89852889

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

015176daea9d84b7482d58b88817bcdbb83fffc59c5bf50d036cff98ffdcb6cd

9a893085ae512735efe66a5d9d76c099e8be9213331496f8b0f09ece85826405

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aaaa89852889 (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 aaaa89852889 across your stack and pipelines.
If you installed it — respond
Remove aaaa89852889 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.
Did it already run?
If aaaa89852889 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 aaaa89852889 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. aaaa89852889 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

RLMA-2025-00047RLUA-2026-10669

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aaaa89852889-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database