Which versions of dependency00011124931 are malicious?

The following PyPI versions of dependency00011124931 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate dependency00011124931 if I installed it?

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

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

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

Malicious package

dependency00011124931PyPI

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

MAL-2024-12253

Immediate action

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

pip uninstall dependency00011124931

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

1.0.1

Indicators of compromise (SHA-256)

936a25f4b0e311939767caf84d7b698d99eab04fdb75dfc8d2e37595a07ef795

8fa6dafeedc48e6511a70676806da412d047f7f235f471a29c98afb9931cbbf2

fe4fbf7a411ba6f163d72d91587edf383ddf00c611f21b311fd94695701139b2

a9fdcfb1731f08b502ef724f11416e2cea13dde887972adb80d4251e4c4f4dc2

5b8d21b44567147defff8b712192abc7488f31f08dec444c7d446c2cf931a2bd

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