What does the testveriftest1asdlaaaaa 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 'testveriftest1asdlaaaaa' @ 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 testveriftest1asdlaaaaa are malicious?

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

How do I remediate testveriftest1asdlaaaaa if I installed it?

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

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

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

Malicious package

testveriftest1asdlaaaaaPyPI

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

MAL-2025-3603

Immediate action

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

pip uninstall testveriftest1asdlaaaaa

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 'testveriftest1asdlaaaaa' @ 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)

43dbf0b3521dc45dbc381810dbbbc059df60c4d723e8fee4169286733d31cf91

4125189a7d4a1fc1734990626f25ee4e49b68590d96a8f0b61a490cb91141a5d

ff36b3e2ad882727ed964a43d4599f3713d2bada89b6cec169d727127c21c2fa

00c91b13bdec38a64b3972a94685ab9bc7de0c9c29b03717824dc6b2b316d962

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