Which versions of gwpythonsectt1 are malicious?

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

How do I remediate gwpythonsectt1 if I installed it?

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

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

Yes — gwpythonsectt1 is associated with the RLMA-2025-03012, GENERIC-standard-pypi-install-pentest, RLUA-2026-00369 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 gwpythonsectt1 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 gwpythonsectt1 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gwpythonsectt1 across your stack and pipelines.

Malicious package

gwpythonsectt1PyPI

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

MAL-2025-5115

Immediate action

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

pip uninstall gwpythonsectt1

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)

de18c7840e01f9830cc8075ca81646ea67486948769fd58d6f99ae58071cd0fa

c805fffe3cc1fb619f0dec2139f2cffeb6b709e857f85f14d49d895457bfcbfd

e725c704d6886238676ace905f16e6ad90eb00884187b18e2225bc66bf3a51cd

b6a9045d673f8b20e47ceaca2ce96738ce3dab0230afa7fb6c76506f84887ca6

016e9298325f4270aa3ec054a4634495f03c92e6ee6a1f7b79a1001c45d1ea63

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gwpythonsectt1 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gwpythonsectt1 across your stack and pipelines.
If you installed it — respond
gwpythonsectt1 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 gwpythonsectt1 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 gwpythonsectt1 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. gwpythonsectt1 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-03012GENERIC-standard-pypi-install-pentestRLUA-2026-00369

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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