Which versions of veriftest1asdla are malicious?

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

How do I remediate veriftest1asdla if I installed it?

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

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

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

Malicious package

veriftest1asdlaPyPI

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

MAL-2025-4251

Immediate action

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

pip uninstall veriftest1asdla

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)

71229f3feb9625f379a5603ccf203fed73803899f88989cf8ac9f786880c5b2d

27df9e17625d7fa74ff728bd8f9cb4784ee934e5277dd1d50df43ef5c54247fe

e04795c3a8f7fae13a125bde307aa64db04ae9f4ff76bd1d11fb32b4d3f57a36

78188a09820df3fbbeafbb6374f13b398ce5d37b502d7de14571e9bcf8e6bee2

578cebe4ea2d52b54edd023a1a24ae65f5b58b9bf90c4c6f2e0c6dcbabbde034

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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