Which versions of soal are malicious?

The following PyPI versions of soal are flagged malicious: 8.0.5. Treat any of these as compromised.

How do I remediate soal if I installed it?

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

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

Yes — soal is associated with the 2024-07-weaponized-golden 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 soal 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 soal (version 8.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soal across your stack and pipelines.

Malicious package

soalPyPI

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

MAL-2024-12345

Immediate action

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

pip uninstall soal

What this malware does

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

Campaign: 2024-07-weaponized-golden

Reasons (based on the campaign):

files-exfiltration

Malicious versions

1 flagged

8.0.5

Indicators of compromise (SHA-256)

e1d1956bd077778dad8ce9574c345abc40d19a36d4b541eb4f4482fdd75efeba

acbef83f8fce2a2944f16812b0a2f89f92b4b0e0902439a4224b7ddd2b516f9b

70abcc26f28cb5946b571b5c122e2a92c0a3cde3a3aa2a0b0c1e9a1364bd9fea

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

Campaign

2024-07-weaponized-golden

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks soal-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