Which versions of awsgluedq are malicious?

The following PyPI versions of awsgluedq are flagged malicious: 0.1.3, 6.1.3, 6.1.4. Treat any of these as compromised.

How do I remediate awsgluedq if I installed it?

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

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

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

Malicious package

awsgluedqPyPI

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

MAL-2025-2941

Immediate action

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

pip uninstall awsgluedq

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

3 flagged

0.1.36.1.36.1.4

Indicators of compromise (SHA-256)

3476f9b372882a86dfaf351fabf0373fb82ccd50fec629e885f70507ed610b4a

e966c7993dc3f177a52d0a1ac9c9b003d9fe90d63d336b5f47d9f64615f0d70d

da16cd67a3672f17d5cce10c5626cf682be33e63db5ca04db645b975afc9bea1

a9d4f4f57cb727ac6db92eff229c562bce5c2a731ea293a7b12805c659617a64

9095efd632861755c361d8eaeb5d4a916eb6940cc7cf09cf6d690ed83783fecd

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

Campaign

RLMA-2025-019392025-01-aws-glueRLUA-2026-00130

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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