Which versions of python-project-wntliogu are malicious?

The following PyPI versions of python-project-wntliogu are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate python-project-wntliogu if I installed it?

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

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

Yes — python-project-wntliogu 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 python-project-wntliogu 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 python-project-wntliogu (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-project-wntliogu across your stack and pipelines.

Malicious package

python-project-wntlioguPyPI

Malicious code in python-project-wntliogu (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12334

Immediate action

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

pip uninstall python-project-wntliogu

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

0.1.0

Indicators of compromise (SHA-256)

c4c1a1e77b0380f7492dd17dbacd1bdac60f9e375c4fa727247017d59da6bf94

82bffbaa9f040ea19ff4e9fe678df68b1be71418f80fcd665ecc4f729512df19

c37e7d19de4e503d1c8d5662d74bb51bdf701989d746d1373e17a0dcc0cf0b8f

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 python-project-wntliogu (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-project-wntliogu across your stack and pipelines.
If you installed it — respond
Remove python-project-wntliogu 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 python-project-wntliogu 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 python-project-wntliogu 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. python-project-wntliogu on PyPI has been identified as a malicious package (version 0.1.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 python-project-wntliogu-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