Which versions of runtimeutils are malicious?

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

How do I remediate runtimeutils if I installed it?

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

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

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

Malicious package

runtimeutilsPyPI

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

MAL-2025-192686

Immediate action

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

pip uninstall runtimeutils

What this malware does

Importing the module, downloads and starts a malicious executable identified as infostealer.

Based on Telegram links, this is related to the 2025-12-synium campaign, but uses slightly different techniques.

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

Campaign: 2025-12-runtimeutils

Reasons (based on the campaign):

malware
Downloads and executes a remote executable.
infostealer

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

4d312906cc585fcd02b2ac0b52bb04a23b0294532e3625c7f5e27bf1e4b51e4a

a5da1962c4896546065e477eae3461c641d8cab05d4fdd375f7b26bef6d502fa

c0aa179cbb808337b4f5012f05c5a6135a6d0990422dc4b3f8149ab1b0af24a9

fac39c3282cf7700b74a786ebcb009bf685ea520f14fa41a9c30205e551dd20b

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 runtimeutils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging runtimeutils across your stack and pipelines.
If you installed it — respond
runtimeutils 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 runtimeutils 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 runtimeutils 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. runtimeutils 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-runtimeutils

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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