Which versions of veriftest1asdl are malicious?

The following PyPI versions of veriftest1asdl are flagged malicious: 1. Treat any of these as compromised.

How do I remediate veriftest1asdl if I installed it?

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

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

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

Malicious package

veriftest1asdlPyPI

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

MAL-2025-4250

Immediate action

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

pip uninstall veriftest1asdl

What this malware does

During installation, the package attempts to exfiltrate cloud tokens

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

Campaign: 2025-05-veriftest1asdl

Reasons (based on the campaign):

exfiltration-cloud-tokens
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

8eed5e3d4db0e9f10578796813f9d6759b65e403a2b4d16cdc9867ba7ca58591

bf0ac9f4340b4df3f61725bc1d9f4a6630f6f42020e9a34b1df378f020fc3c41

e11e583c94e6aea422cd70561ea53212b4b4a26dd4bcb2e42c4c1ad25066474d

9b8a8c57fb69507f006fa612164a57b65771f2325079b67ebc9d22bcb6f87e12

afc5f2c103df89d7cd57f45ac732160b5517758c92cc2c1542e4890adfe637a3

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

Campaign

RLMA-2025-026082025-05-veriftest1asdlRLUA-2026-00885

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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