Which versions of aws-glue are malicious?

The following PyPI versions of aws-glue are flagged malicious: 6.1.4, 6.1.5. Treat any of these as compromised.

How do I remediate aws-glue if I installed it?

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

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

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

Malicious package

aws-gluePyPI

Malicious code in aws-glue (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2940

Immediate action

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

pip uninstall aws-glue

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

2 flagged

6.1.46.1.5

Indicators of compromise (SHA-256)

7df756fdf799f637cc63cb3ba9ed8f0a9492630d6e70765bd9595799bcf88271

01873cd0a0165ba90c6ed256a1c91afadf2328a1e2c29b668c635feb3f811f99

96424ced6ac0c4b9f671c5f7f03b4b99f7354e1eb2c48aba76f405f078a62ec6

b9b6c2557596969a3b80c546fff76ac5010130b772ac3b21588d65d9dad3c613

39023c6cf531b2f8c8f82a9723f80130f0d34b1f9676896bbe449b85a676bae7

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

Campaign

RLMA-2025-019382025-01-aws-glueRLUA-2026-00129

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks aws-glue-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