Which versions of awsglueml are malicious?

The following PyPI versions of awsglueml are flagged malicious: 6.1.4. Treat any of these as compromised.

How do I remediate awsglueml if I installed it?

Remove awsglueml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — awsglueml is associated with the RLMA-2025-01940, 2025-01-aws-glue, RLUA-2026-00131 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 awsglueml 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 awsglueml (version 6.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awsglueml across your stack and pipelines.

Malicious package

awsgluemlPyPI

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

MAL-2025-2942

Immediate action

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

pip uninstall awsglueml

What this malware does

This is a couple of packages with names appearing to be a library for an AWS or other service. Their only behaviour is to call home on installation or import

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-01-aws-glue

Reasons (based on the campaign):

dependency-confusion

Malicious versions

1 flagged

6.1.4

Indicators of compromise (SHA-256)

913e21ddde38677fb3dc0c0d5d84018b525d783fc1f2d43a3e312e5fb18e6856

78c9ac30ebfd4bfea96a2f5cfc59de7a4871bc89f52c72ffb5b4a8d3bf009147

8a7eb55169fa28d500f750382641170b6a921f1ebca4e715a10d33b05ff78f8b

6f8ec775736763cecadb85a3cb7004ee518775d946fe7ab6474dfbcdbc5f58be

b5dc6006e591dc367a05c906bdbb22766b63de4736a6c43e0226c8c0f76b2afe

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for awsglueml (version 6.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awsglueml across your stack and pipelines.
If you installed it — respond
Remove awsglueml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If awsglueml 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 awsglueml 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. awsglueml on PyPI has been identified as a malicious package (version 6.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-019402025-01-aws-glueRLUA-2026-00131

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks awsglueml-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring