Which versions of boost-tool-api are malicious?

The following PyPI versions of boost-tool-api are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate boost-tool-api if I installed it?

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

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

Yes — boost-tool-api is associated with the RLMA-2024-03607, RLUA-2024-07887 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 boost-tool-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for boost-tool-api (version 1.0).

Malicious package

boost-tool-apiPyPI

boost-tool-api is a confirmed malicious PyPI package (MAL-2024-4827) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boost-tool-api (PyPI)

MAL-2024-4827

Immediate action

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

pip uninstall boost-tool-api

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

f64bac8f12c0ddcf32e6848e70668d201b7603be1c4ddeca618a50dbe20005d3

0b48f244b270864b8ea4f5842fa69fc649824ef66297e3b164a46bbbf05130e8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03607RLUA-2024-07887

References

research.jfrog.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks boost-tool-api-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