Which versions of gltest are malicious?

The following PyPI versions of gltest are flagged malicious: 2.0. Treat any of these as compromised.

How do I remediate gltest if I installed it?

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

If gltest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is gltest part of a known attack campaign?

Yes — gltest is associated with the GENERIC-simple-tests 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 gltest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gltest (version 2.0).

Malicious package

gltestPyPI

Advisory published Aug 23, 2024Updated Mar 17, 2026

gltest is a confirmed malicious PyPI package (MAL-2024-12278) that executes malicious code on install (malicious version 2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gltest (PyPI)

MAL-2024-12278

Immediate action

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

pip uninstall gltest

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

2.0

Indicators of compromise (SHA-256)

953fa9f478f5d4ee25d85fefe83ab76bc24bc378127c56fee2486e89ef1b4248

538a0e3540a764042a57930b8729d61b05747d057875504da316d6ee14bf91fd

c2449c1b04e3cd301e2d2df4d2862ee66ed14b77e459eb1b31c73b1688ca68aa

7d3ef862309a888264d720acde53792700ab5b4c6c8f0690e69a502d8e833ad5

7c587be8bc908391a1dbccc0a63e24eabe2314692dcf06ffb705ee1d1714d358

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gltest (version 2.0).
If you installed it — respond
Remove gltest 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 gltest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. gltest on PyPI has been identified as a malicious package (version 2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database