Which versions of testpackagemanyhttpsgo are malicious?

The following PyPI versions of testpackagemanyhttpsgo are flagged malicious: 2.26. Treat any of these as compromised.

How do I remediate testpackagemanyhttpsgo if I installed it?

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

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

Yes — testpackagemanyhttpsgo is associated with the 2026-06-easyaillm, IN-MAL-2026-006743 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 testpackagemanyhttpsgo 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 testpackagemanyhttpsgo (version 2.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testpackagemanyhttpsgo across your stack and pipelines.

Malicious package

testpackagemanyhttpsgoPyPI

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

MAL-2026-5840

Immediate action

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

pip uninstall testpackagemanyhttpsgo

What this malware does

At install time, setup.py fetches https://tmpfiles.org/dl/wawHVGgfydD7/6a306c5f03a52.exe via urllib, writes the response to disk, and executes it with os.system("cmd /c start 6a306c5f03a52.exe"). tmpfiles.org is an anonymous, throwaway file-hosting service; the URL is unpinned and unverified, the payload is an opaque Windows executable, and the package's metadata (author and description both equal to the package name) is placeholder content consistent with a throwaway publisher account. Any Windows host running pip install for this package will fetch and execute attacker-controlled bytes automatically, with no opt-in or verification.

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

2.26

Indicators of compromise (SHA-256)

e58c0178b75445617a5eb6ea340e797c86e324d07063e57b9fc4d3eaa5e2c0d9

336f39e218fe5b5a09ef8ee7757efa7a0ca73c0fe6571bc232d735448499a950

559b34e692c8774c8d4e07cda7c26abefcb40c559158bbdf0179710702ddcca4

d330f7ba94bdfb53c05235fa9b278688ada43c2fe207ccc51e977afbc227333c

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 testpackagemanyhttpsgo (version 2.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testpackagemanyhttpsgo across your stack and pipelines.
If you installed it — respond
testpackagemanyhttpsgo 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 testpackagemanyhttpsgo 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 testpackagemanyhttpsgo 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. testpackagemanyhttpsgo on PyPI has been identified as a malicious package (version 2.26 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-easyaillmIN-MAL-2026-006743

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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