Which versions of veriftest1asdlaa are malicious?

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

How do I remediate veriftest1asdlaa if I installed it?

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

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

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

Malicious package

veriftest1asdlaaPyPI

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

MAL-2025-4252

Immediate action

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

pip uninstall veriftest1asdlaa

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)

1b637184b9d883cb951f1bb4073daac9b99fc6168afd647260107263417f9553

a359e90cf6e8e4eb2550f45ab37e7c158340289f197afa4a1fd9f02e15813f14

84fe70a8f5e34c8334d7284bcc9b71826210f029708a53a6ec4b9bb90a33054b

3c817167e6beba41942a8bdf03dacc5287f67a3b7919a99d6ef2b0982962a24f

e65ce8aed2feffa9d8553e15522a35251c27539071aa3ff7b073d74fdb9b04ae

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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