Which versions of awsutil are malicious?

The following PyPI versions of awsutil are flagged malicious: 0.1.0, 0.1.1, 99.99.99. Treat any of these as compromised.

How do I remediate awsutil if I installed it?

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

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

Yes — awsutil is associated with the 2025-12-sec-lab-it 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 awsutil 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 awsutil (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awsutil across your stack and pipelines.

Malicious package

awsutilPyPI

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

MAL-2025-192961

Immediate action

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

pip uninstall awsutil

What this malware does

Dependency confusion research package with advanced module-mocking

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-12-sec-lab-it

Reasons (based on the campaign):

dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting

Malicious versions

3 flagged

0.1.00.1.199.99.99

Indicators of compromise (SHA-256)

86d4af9fafbcfb6e3789a38b426c744e4ac67da10eb1fa225be3a715189fb1c2

a5e82ba558a433d625bbaf8e06e6f6c7edfcdfd93735be5448761ce39949043f

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 awsutil (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awsutil across your stack and pipelines.
If you installed it — respond
awsutil 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 awsutil 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 awsutil 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. awsutil on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-sec-lab-it

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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