What does the bola511 malware do?

The package bola511 was found to contain malicious code. The OpenSSF Package Analysis project identified 'bola511' @ 99.99.99 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of bola511 are malicious?

The following npm versions of bola511 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate bola511 if I installed it?

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

If bola511 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.

How do I find bola511 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bola511 (version 99.99.99).

Malicious package

bola511npm

Advisory published Dec 26, 2025Updated Jan 2, 2026

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

Malicious code in bola511 (npm)

MAL-2025-192941

Immediate action

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

npm uninstall bola511

What this malware does

The package bola511 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bola511' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

eea756cc3e9de36a5fb64a18448c1134945c9e97ac25b152267025711e700410

adc760a1f5b29980f41bbd685a2472e4f835f234b483c17520a81c1c881ca420

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bola511 (version 99.99.99).
If you installed it — respond
Remove bola511 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 bola511 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. bola511 on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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