Which versions of amazon-boto are malicious?

The following PyPI versions of amazon-boto are flagged malicious: 1.42.41, 1.42.42. Treat any of these as compromised.

How do I remediate amazon-boto if I installed it?

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

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

Yes — amazon-boto is associated with the 2025-08-aws-enumerate 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 amazon-boto across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for amazon-boto (2 malicious versions).

Malicious package

amazon-botoPyPI

Advisory published Apr 29, 2026Updated Apr 29, 2026

amazon-boto is a confirmed malicious PyPI package (MAL-2026-3148) that steals credentials and exfiltrates sensitive data (malicious versions 1.42.41, 1.42.42). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in amazon-boto (PyPI)

MAL-2026-3148

Immediate action

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

pip uninstall amazon-boto

What this malware does

When using the package, the given AWS credentials are silently exfiltrated to a hardcoded location. This incarnation of the long-running campaign was first flagged by OpenSourceMalware https://opensourcemalware.com/pypi/amazon-boto

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

Campaign: 2025-08-aws-enumerate

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage
exfiltration-credentials

Malicious versions

2 flagged

1.42.411.42.42

Indicators of compromise (SHA-256)

649bb559f3078565515a9fee16dbe78e0d1b5575943cbaf020135f8e70e2f17d

Detection & response playbook

Credential / info stealer

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

Campaign

2025-08-aws-enumerate

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks amazon-boto-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