Which versions of initialtestingdonotpull1235 are malicious?

The following PyPI versions of initialtestingdonotpull1235 are flagged malicious: 3.0.1. Treat any of these as compromised.

How do I remediate initialtestingdonotpull1235 if I installed it?

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

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

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

Malicious package

initialtestingdonotpull1235PyPI

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

MAL-2025-41435

Immediate action

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

pip uninstall initialtestingdonotpull1235

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.

The OpenSSF Package Analysis project identified 'initialtestingdonotpull1235' @ 3.0.1 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

3.0.1

Indicators of compromise (SHA-256)

a9622e8d5bdc036e8502ca1158478c805862e882dc7a27f493b01dff9ae76115

ec2eaf178a4fdaf3ce8ed1037695ce3d903c6b425b714026bc3ed26980ec6673

638020a87c6e1aaf4b8542a5b20723a6ed900b986bfd407c8bf55aad3016933f

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 initialtestingdonotpull1235 (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging initialtestingdonotpull1235 across your stack and pipelines.
If you installed it — respond
initialtestingdonotpull1235 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 initialtestingdonotpull1235 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 initialtestingdonotpull1235 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. initialtestingdonotpull1235 on PyPI has been identified as a malicious package (version 3.0.1 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)
OpenSSF: Package Analysis · finder

Detect & block this

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