Malicious code in aet-test (PyPI)
The aet-test package on PyPI contained malicious code that exfiltrates basic host information (IP address, username) during installation. The package overrides the install command in setup.py to execute the malicious payload.
- Disclosed
- Last updated
- Blast radius
- Limited to users who installed the malicious aet-test package from PyPI.
- Ecosystems
- Attack vectors
- Affected entities
- aet-testMalicious package on PyPI
The aet-test package published on PyPI was identified as containing malicious code designed to exfiltrate basic system information from the host upon installation or module import. The malicious functionality includes capturing data such as the system's IP address and username.\n\nThe attack was implemented by overriding the install command in setup.py, allowing the malicious code to execute during the package installation process. This is a common technique for supply chain attacks targeting Python package managers.\n\nThe package was classified as a low-harm pentest-style package with limited risk scope, as it only performs basic data exfiltration without additional destructive capabilities. The incident was identified and documented by the OpenSSF malicious-packages project.\n\nUsers who installed this package should assume their basic system information (IP address, username) may have been exfiltrated and should monitor for any suspicious activity.
Indicators of compromise
- Packages
- aet-test
Remediation
- Uninstall the aet-test package immediately using 'pip uninstall aet-test'
- Review PyPI package installation logs to identify when the malicious package was installed
- Assume basic host information (IP, username) has been compromised and monitor for related suspicious activity
- Check for any other suspicious packages installed around the same time
- Use package verification tools and only install packages from trusted sources
- Consider using dependency scanning tools to detect similar malicious packages in your environment
Sources
- GitHub Advisory GHSA-3c39-8x8m-9hhr · GitHub Advisory Database
Cite this entry
"Malicious code in aet-test (PyPI)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 21, 2026; last updated July 21, 2026. https://supplychainattack.org/incident/malicious-code-in-aet-test-pypi-1t6vqe
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in afrit-name (PyPI)
Malicious code was discovered in the afrit-name package on PyPI. The incident was identified and documented by the OpenSSF malicious packages project.
PyPICompromised package - resolvedcritical
Malicious code in adv2099m7 (PyPI)
Malicious code was discovered in the adv2099m7 package on PyPI. The package was identified and cataloged by the OpenSSF malicious packages project.
PyPICompromised package - resolvedcritical
Malicious code in adrandom (PyPI)
The adrandom package on PyPI contained malicious code that executed spyware and information-stealing malware. It was part of a campaign by the EsqueleSquad group that published nearly 6,000 malicious packages across PyPI and NPM.
EsquelesquadPyPICompromised package - resolvedcritical
Malicious code in ziphash (PyPI)
The ziphash package on PyPI contained malicious code that downloads and executes multi-stage malware during archive-support class initialization. The malware exhibits obfuscation and remote code execution capabilities, classified as part of the 2025-11-uzip campaign.
2025 11 UzipPyPICompromised package