Which versions of booms-ai are malicious?

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

How do I remediate booms-ai if I installed it?

Remove booms-ai 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 booms-ai — how do I know if it already compromised me?

If booms-ai 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.

Is booms-ai part of a known attack campaign?

Yes — booms-ai is associated with the RLMA-2025-06070 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 booms-ai across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for booms-ai (version 1.0.0).

Malicious package

booms-ainpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

booms-ai is a confirmed malicious npm package (MAL-2025-192715) 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 booms-ai (npm)

MAL-2025-192715

Immediate action

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

npm uninstall booms-ai

What this malware does

The package booms-ai was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ae3d0071a3369601376b6e4688cc67aada7da30045b4c9bc83a6176958542c07

b4f369d319c15da73192ca2b5c7df90f0699660467e1c379f08682ca0eb346a4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for booms-ai (version 1.0.0).
If you installed it — respond
Remove booms-ai 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 booms-ai 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. booms-ai 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-06070

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks booms-ai-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