Which versions of synium are malicious?

The following PyPI versions of synium are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate synium if I installed it?

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

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

Yes — synium is associated with the 2025-12-synium 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 synium 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 synium (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging synium across your stack and pipelines.

Malicious package

syniumPyPI

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

MAL-2025-192438

Immediate action

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

pip uninstall synium

What this malware does

During import, package exfiltrates specific global variables to a remote target in a way typical for infostealers

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

Campaign: 2025-12-synium

Reasons (based on the campaign):

exfiltration-credentials
exfiltration-generic

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

85fc917c33d970cb3365ff112f788b229638b757c32eaf99ba1054c8596298c1

eb09648d942b8841b8a2258de694ebc78231e14635fe0c1cb17d88f7a1d14eb6

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

Campaign

2025-12-synium

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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