Which versions of veriftest1asdlaaa are malicious?

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

How do I remediate veriftest1asdlaaa if I installed it?

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

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

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

Malicious package

veriftest1asdlaaaPyPI

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

MAL-2025-4253

Immediate action

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

pip uninstall veriftest1asdlaaa

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)

bd37166c95b260a650c6fb2c96e2da5eae8b7cda8ccb7384b506d4a1c39ade68

8953c802be029ee2cf0c07fc075ee62ad7b6170eabf4996f4e78266a089b8c07

8ca63296b7d7f9b656944bcaf65cc918b709a2071d1ea5f16d1a7422a9df931e

0b1c39a6af7a9b591a2624cef50f3984f09f5144225dbb34a6c626a376c7af1b

1e28765b13dc5a1d0474caac0adc41e2a80f1facea8cda1cc7ad8ac1173b5dba

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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