Which versions of amzn-awsglue are malicious?

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

How do I remediate amzn-awsglue if I installed it?

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

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

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

Malicious package

amzn-awsgluePyPI

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

MAL-2025-2936

Immediate action

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

pip uninstall amzn-awsglue

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)

b411d9951b7f09768d7d19422c03f911ebc0c765ec5626d36e57568399fabf5f

6ac406663865df7beea17e1da30b3e3b2be4aa6257ba51b5ec85be6b94b0333e

d53712580b3109807a0911c66dab7e45fa9f2968c76e2f31b5f0a23d23b03373

1d4152cd8d75cb6cfd8446a845220ae7fda65a74856c16d649b7019ecd60dc69

bd066b8cd3f72d382570ba690c249fc8984c44bd197543d325803f29e1d7b771

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 amzn-awsglue (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amzn-awsglue across your stack and pipelines.
If you installed it — respond
Remove amzn-awsglue 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 amzn-awsglue 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 amzn-awsglue 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. amzn-awsglue 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-019342025-01-aws-glueRLUA-2026-00063

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks amzn-awsglue-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