Which versions of ninjainjtest1337 are malicious?

The following PyPI versions of ninjainjtest1337 are flagged malicious: 0.1.0, 0.1.1, 0.1.3, 0.1.4, 0.1.5, 0.1.6. Treat any of these as compromised.

How do I remediate ninjainjtest1337 if I installed it?

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

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

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

Malicious package

ninjainjtest1337PyPI

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

MAL-2025-1514

Immediate action

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

pip uninstall ninjainjtest1337

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.

The OpenSSF Package Analysis project identified 'ninjainjtest1337' @ 0.1.5 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

6 flagged

0.1.00.1.10.1.30.1.40.1.50.1.6

Indicators of compromise (SHA-256)

334ea071d3d2127435d95bdf47129449b33f6c542fe9c91d19d4c5365f86d77f

7dc9c53dc88e1b23e6a443eb6820f89d5b866c8e610b0c8b3ab69a534799f7c1

fd7c71e57cd743cb8de4b5f52f3be1f4956e0fd105748b3d047834068011926b

25f834fdd3843d8d1bb3c977e15adea6465c662a69b3d85c9ceb492e38e7a60a

53b486443b3f2ffe278aa364b7455c2a522fbf1a514d4c8f70474974bf2be009

0373c0945e8f1956caa05c9ae65b6152468adf11bf504159f0829ad4dcfcf3f8

0057edfac0d3f5184a3a41c9574865cb18ec8fc6b2128d8ca356677c9e223190

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

Detect & block this

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