Which versions of audit-themis-i18n are malicious?

The following PyPI versions of audit-themis-i18n are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate audit-themis-i18n if I installed it?

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

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

Yes — audit-themis-i18n is associated with the 2024-08-byted-22.ax 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 audit-themis-i18n 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 audit-themis-i18n (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging audit-themis-i18n across your stack and pipelines.

Malicious package

audit-themis-i18nPyPI

Malicious code in audit-themis-i18n (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12210

Immediate action

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

pip uninstall audit-themis-i18n

What this malware does

Collects basic information about the system, most probably a pentest or bug bounty.

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: 2024-08-byted-22.ax

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.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

9e23a1115e08d97f16646cffbb461344e40dc97526c84c1d66fa638d94b3ba32

37f93a88c028e5f97cf3f81fbfea413f78a01ea84f108247d6d5abf926f0dd73

234240ae56e865435e855d9fffc30c622100feb5fe6aab37b43ba5f120ce3ed4

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

Campaign

2024-08-byted-22.ax

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks audit-themis-i18n-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