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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for blackamerxs (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blackamerxs across your stack and pipelines.

Malicious package

blackamerxsPyPI

Malicious code in blackamerxs (PyPI) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for blackamerxs (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blackamerxs across your stack and pipelines.
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 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 blackamerxs 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. 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