Which versions of blackamerxs are malicious?

The following PyPI versions of blackamerxs are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate blackamerxs if I installed it?

blackamerxs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — blackamerxs is associated with the RLMA-2024-10982, 2024-11-blackamerxs, RLUA-2026-00151 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 blackamerxs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for blackamerxs (version 0.1).

Malicious package

blackamerxsPyPI

Advisory published Nov 22, 2024Updated Mar 19, 2026

blackamerxs is a confirmed malicious PyPI package (MAL-2024-11537) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blackamerxs (PyPI)

MAL-2024-11537

Immediate action

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

pip uninstall blackamerxs

What this malware does

If run, the code in the package exfiltrates all files from the current directory tree.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-11-blackamerxs

Reasons (based on the campaign):

files-exfiltration

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

884bbb3b0c79586c36206c3b35fce744914e2e3bc925806d818554e2db9664b1

76667e7e9f568693354205ad5caa94f043683bfc61da1513e050a06a84410f1d

50486a7fa5636706a3c90bf515f6664c6cbb11aa127f9b3e95d7b38cf89c80c8

79e5fec7221131f1ce6b209da71b845fb9abfa529a55d14a9bcb2b98e0ea0cbc

6c182d46c57239d916279e9b4b83fbccc39d071005612c65f18e99e218ef720d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for blackamerxs (version 0.1).
If you installed it — respond
blackamerxs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If blackamerxs 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. blackamerxs on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-109822024-11-blackamerxsRLUA-2026-00151

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks blackamerxs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database