Which versions of financial-crimes-general-utils are malicious?

The following PyPI versions of financial-crimes-general-utils are flagged malicious: 3.9.12. Treat any of these as compromised.

How do I remediate financial-crimes-general-utils if I installed it?

financial-crimes-general-utils 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 financial-crimes-general-utils — how do I know if it already compromised me?

If financial-crimes-general-utils 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 financial-crimes-general-utils part of a known attack campaign?

Yes — financial-crimes-general-utils is associated with the 2026-02-urllib-slim 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 financial-crimes-general-utils 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 financial-crimes-general-utils (version 3.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging financial-crimes-general-utils across your stack and pipelines.

Malicious package

financial-crimes-general-utilsPyPI

Malicious code in financial-crimes-general-utils (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2107

Immediate action

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

pip uninstall financial-crimes-general-utils

What this malware does

In specific environments, during installation, the package attempts to exfiltrate some basic information using DNS requests and then cover tracks by installing a similarly named package from the local private repository

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

Campaign: 2026-02-urllib-slim

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
obfuscation
dependency-confusion

Malicious versions

1 flagged

3.9.12

Indicators of compromise (SHA-256)

21f201c2aada618cb80f926b029f6b83b3f3bd9ffd0b35d5a4bb0c3aa1afd792

0a25418866ddab42755c1e981f2db0a0b6a8f49fc0635ee981ee6c36dff35b09

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

Campaign

2026-02-urllib-slim

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks financial-crimes-general-utils-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