Which versions of ninja-core-optimizer are malicious?

The following PyPI versions of ninja-core-optimizer are flagged malicious: 1.3.3, 1.3.4. Treat any of these as compromised.

How do I remediate ninja-core-optimizer if I installed it?

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

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

Yes — ninja-core-optimizer is associated with the 2026-05-ninja-core-utils 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 ninja-core-optimizer 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 ninja-core-optimizer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ninja-core-optimizer across your stack and pipelines.

Malicious package

ninja-core-optimizerPyPI

Malicious code in ninja-core-optimizer (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3396

Immediate action

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

pip uninstall ninja-core-optimizer

What this malware does

During installation, obfuscated code exfiltrates cryptocurrency wallet data to a hardcoded location

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-ninja-core-utils

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
crypto-related
exfiltration-crypto
backdoor

Malicious versions

2 flagged

1.3.31.3.4

Indicators of compromise (SHA-256)

7421b043b7d687849d0a75da8ecf204604e61b20efc5cf5b18bd3648225e4011

fbe38f659a9fac5304f648aa594e12123221abd687755378f05b3efe17d6d4c7

f3b0b000f1baa5e720574c744c51968be3cd230bf5a4d8b451ddf0709e87d2f0

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 ninja-core-optimizer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ninja-core-optimizer across your stack and pipelines.
If you installed it — respond
ninja-core-optimizer 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 ninja-core-optimizer 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 ninja-core-optimizer 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. ninja-core-optimizer on PyPI has been identified as a malicious package (versions 1.3.3, 1.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-ninja-core-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ninja-core-optimizer-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