Which versions of veriftest1asdlaaaa are malicious?

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

How do I remediate veriftest1asdlaaaa if I installed it?

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

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

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

Malicious package

veriftest1asdlaaaaPyPI

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

MAL-2025-4254

Immediate action

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

pip uninstall veriftest1asdlaaaa

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)

14006d51a1c0401267f0cde60e05a37e4f73cdccc8d411beab2a87334f248dab

b92f906eae88df2f6c2e96a57b2d258e815305abe81fab70fecee74b819da73c

18d30d48c72a61cda2e8b0ecd3a27b958e8964b4c65833cb780186382285101d

a213b19e8ffaf71235072fe1ae7f0282ee5c8ca457aa873ccb31d5955b314b26

f19843d6dc712a5df94bd61a64df361987d7919eb999f05800c3f1947107a368

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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