Which versions of doverius are malicious?

The following PyPI versions of doverius are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate doverius if I installed it?

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

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

Yes — doverius is associated with the RLMA-2025-03587, 2025-06-justanything, RLUA-2026-00281 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 doverius 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 doverius (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging doverius across your stack and pipelines.

Malicious package

doveriusPyPI

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

MAL-2025-6496

Immediate action

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

pip uninstall doverius

What this malware does

Code is designed to download and run remote scripts during installation, which finally downloads and starts an infostealer

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

Campaign: 2025-06-justanything

Reasons (based on the campaign):

infostealer
The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote malicious script.
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

d85221993acc2bc24d90da7d3b15ce9ca172446cff60a2bb1c87dc146b8dd050

d4ab7f4df36b800e0eaf41f4d455f5807675d15ca6ed00a7633b4afb6063f5da

c386579381491132baf4d7848ddb82f965c540fb732abb69771325665eabbc63

67aa21110aecd06adf09f870bd878d943e6ab92f6f0c563b8d2640235277238f

9a2f5e82d385b51cbdf0ce96a9f34f933227730fd2a92625b67f7936740877c8

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

Campaign

RLMA-2025-035872025-06-justanythingRLUA-2026-00281

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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