Which versions of modelconftranslator are malicious?

The following PyPI versions of modelconftranslator are flagged malicious: 8.13.4. Treat any of these as compromised.

How do I remediate modelconftranslator if I installed it?

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

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

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

Malicious package

modelconftranslatorPyPI

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

MAL-2026-2108

Immediate action

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

pip uninstall modelconftranslator

What this malware does

During installation, the package starts obfuscated code that downloads and runs remote executables in specific environments - in older packages - attempts to exfiltrate some basic information using DNS requests and then likely cover tracks by installing a similarly named package from 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

8.13.4

Indicators of compromise (SHA-256)

6f61fcbf30122cbf577490fab3968c6b41f95d4d23f6916a7211066bd735ff6e

3e044e5a77e116a3c892a4190bf3671c28005c9687da613b83969372b7fe02f2

e1d918db23be048d16eb2c61f1dd164b1e752aa80565b7a01fa31cda7cdf3115

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 modelconftranslator (version 8.13.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging modelconftranslator across your stack and pipelines.
If you installed it — respond
modelconftranslator 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 modelconftranslator 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 modelconftranslator 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. modelconftranslator on PyPI has been identified as a malicious package (version 8.13.4 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 modelconftranslator-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