What does the testveriftest1asdlaaaa malware do?

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. The OpenSSF Package Analysis project identified 'testveriftest1asdlaaaa' @ 1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of testveriftest1asdlaaaa are malicious?

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

How do I remediate testveriftest1asdlaaaa if I installed it?

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

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

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

Malicious package

testveriftest1asdlaaaaPyPI

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

MAL-2025-3602

Immediate action

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

pip uninstall testveriftest1asdlaaaa

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.

The OpenSSF Package Analysis project identified 'testveriftest1asdlaaaa' @ 1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

f038353a795c169c81650e7566b947bfddc4dcf48ad65eba74173d228bae2939

b4e69cdec1c0ace2105b57e6f6e8c778fc8a00a2a645a89072974be3f867678e

3b241cae62c005e3cd31a8251941ab101ebcca75aa4c8cb988905e87529339cd

b7ff08b99f2d0dc85260eb0189fd79c36cd609850bb09ae0691abd2e757bd6c5

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

2025-05-veriftest1asdl

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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