Which versions of inkpy-jinja are malicious?

The following PyPI versions of inkpy-jinja are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate inkpy-jinja if I installed it?

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

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

Yes — inkpy-jinja is associated with the 2025-02-pxz 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 inkpy-jinja 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 inkpy-jinja (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging inkpy-jinja across your stack and pipelines.

Malicious package

inkpy-jinjaPyPI

Malicious code in inkpy-jinja (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191766

Immediate action

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

pip uninstall inkpy-jinja

What this malware does

Packages are designed to collect basic info about the user when importing them, and have no other purpose. While they claim to do so, some packages from the same uploader use confusing names, clearly suggesting the intention to harvest data from unintentional installations.

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: 2025-02-pxz

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.
typosquatting

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cacd5751ee0ea897ecc3100ba6f897ff47380425d380af50cbf0679066cdd3fe

c230bd12491edc91bbbc1080b2d650c4889a8b9269b85a346839a32900bfad2b

70caa81d89ecbf4ade2446cd6f4899bbe8efc55ddaa9bd9e32a3c9a4a4ff5698

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

Campaign

2025-02-pxz

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks inkpy-jinja-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