Two malicious versions of Microsoft's agent-framework package (1.26.1 and 1.26.2) were published on PyPI on November 17, 2026.
Both releases executed arbitrary code on Python startup via malicious.pth files, with version 1.26.2 also requesting GitHub Actions OIDC tokens.
The packages lacked matching GitHub source tags and were removed within an hour.
The problematic versions, numbered 1.26.1 and 1.26.2, were uploaded to the platform at 20:35 and 21:08 UTC respectively. Both were removed before 21:30 UTC. The regular version of the library records around 41.000 downloads per week, although it is not clear how many users managed to download the infected files.
How the identity theft worked
Both fake versions placed a special configuration file in the installation folder to automatically execute hidden code whenever any Python program was started. Version 1.26.1 used the files agent_framework_meta.pth and _telemetry.py, while version 1.26.2 used af_runtime_diag.pth and af_runtime_diag.py.
This code searched system folders, environment variables, and local files for sensitive data. It targeted tools such as Azure CLI, Azure DevOps, Git, Docker, npm, and environment configuration files. The second infected version had an additional capability, requesting temporary digital authentication keys for GitHub actions.
Where did the stolen data end up?
According to researchers at Wiz, the data collected was compressed, encrypted, and automatically sent to a specific web address that offers a free request storage service. The researchers identified fewer than 50 requests to that destination in total.
↳
READ ALSO
HACKS.GR / RELATED
Cyber Attacks & Data Breaches
Researchers claim to have discovered security vulnerabilities in Telegram widgets
↗
The infected versions appeared under the legitimate name of the official Microsoft publisher. However, researchers did not find a corresponding version or source code files in the company's official GitHub repository, suggesting that the publication may have been done by bypassing normal procedures, although the exact method remains unclear.
What should those affected do?
Experts recommend that administrators look for traces of versions 1.26.1 or 1.26.2 in logs, local settings, and caches. Those who find the infected files are urged to isolate computers, rebuild their systems from clean copies, set version 1.26.0 as the safe option again, revoke any exposed passwords or keys, and check cloud activity logs.
>Stay connected with Hacks.gr
Set us as a preferred source on Google and find us on social media.
Preferred source
↗
end of article
Top comments (0)