Which versions of gwpythonsectt2 are malicious?

The following PyPI versions of gwpythonsectt2 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate gwpythonsectt2 if I installed it?

gwpythonsectt2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — gwpythonsectt2 is associated with the RLMA-2025-03013, GENERIC-standard-pypi-install-pentest, RLUA-2026-00370 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 gwpythonsectt2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gwpythonsectt2 (version 0.1).

Malicious package

gwpythonsectt2PyPI

Advisory published Jul 26, 2024Updated Mar 19, 2026

gwpythonsectt2 is a confirmed malicious PyPI package (MAL-2025-5116) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gwpythonsectt2 (PyPI)

MAL-2025-5116

Immediate action

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

pip uninstall gwpythonsectt2

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

b75156b36a2e4d482e878addc1747f4edbd5c23035a75765c55f027af340777e

06e6a07575cdefeb5a786ef452462b48acddb1b0a77343f5d98b74d56ce4cafa

cbfa0f91f8c3bb4e7c3ebed7676d1e4c69546c214db5a69e216597ecc367c700

8a8294853a418584e26f2d5d6c41db1ae46b707d3f506bfc085e84812456d8de

f34893d530270348b5883e8d5b0552ef573912f9ea755e480d68eb0f9bf2ce5f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gwpythonsectt2 (version 0.1).
If you installed it — respond
gwpythonsectt2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If gwpythonsectt2 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. gwpythonsectt2 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03013GENERIC-standard-pypi-install-pentestRLUA-2026-00370

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks gwpythonsectt2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database