Which versions of init2winit are malicious?

The following PyPI versions of init2winit are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate init2winit if I installed it?

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

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

Yes — init2winit is associated with the GENERIC-standard-pypi-install-pentest 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 init2winit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for init2winit (version 9.9.9).

Malicious package

init2winitPyPI

Advisory published Mar 20, 2026Updated Mar 20, 2026

init2winit is a confirmed malicious PyPI package (MAL-2026-1989) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in init2winit (PyPI)

MAL-2026-1989

Immediate action

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

pip uninstall init2winit

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

9.9.9

Indicators of compromise (SHA-256)

7eb9b716534151a8d16432102f52af1e6f61f9701b86efba4294cdc0e18ceaea

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for init2winit (version 9.9.9).
If you installed it — respond
init2winit 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 init2winit 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. init2winit on PyPI has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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