Which versions of optimal-spark-config are malicious?

The following PyPI versions of optimal-spark-config are flagged malicious: 14.0.0, 14.0.1, 14.0.2, 14.0.3. Treat any of these as compromised.

How do I remediate optimal-spark-config if I installed it?

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

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

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

Malicious package

optimal-spark-configPyPI

Malicious code in optimal-spark-config (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1222

Immediate action

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

pip uninstall optimal-spark-config

What this malware does

During installation, the package starts obfuscated code that 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

4 flagged

14.0.014.0.114.0.214.0.3

Indicators of compromise (SHA-256)

a1c1bf78d6e3b593fd29329b4175a48c645abf4b4b63e93db68f25221329d14c

8875cb0d0b4757cf1cdaed6b5311cf6b8c841dc2065f824a430a0d0debfaaf22

06464a6f0ed327a7db87798c5134f72c4e43b71eda981f62e8d0549cd13c9eaa

fb399f8b1478c484f6f15ea4541ed99000468a1e737487d4680e1bb43f7d3860

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