Which versions of brummatts are malicious?

The following PyPI versions of brummatts are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate brummatts if I installed it?

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

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

Yes — brummatts is associated with the 2026-10-voice-synthesis-profiles 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 brummatts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for brummatts (version 0.1.0).

Part of a larger attack: 2026-10-voice-synthesis-profiles published 43 malicious packages. See the full campaign →

Malicious package

brummattsPyPI

Advisory published Oct 21, 2026Updated Oct 22, 2026

brummatts is a confirmed malicious PyPI package (MAL-2026-18136) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in brummatts (PyPI)

MAL-2026-18136

Immediate action

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

pip uninstall brummatts

What this malware does

This campaign consists of similar loader packages, which provide executing code from a given URL. While they do not contain the malicious payload and the usage remains unknown, they are clearly a coordinated campaign to place multiple deceptive ways to load malicious code.

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

Campaign: 2026-10-voice-synthesis-profiles

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
other

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

605ea05e6c6344e7ddfb713297d7689ee050288b74ecbf0821039603dc3cdd45

3f8db224d6e3b0f2e94c2b84f1e4f85b54350f63839e4126145109f557068bb5

Detection & response playbook

Credential / info stealer

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

Campaign

2026-10-voice-synthesis-profiles

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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