Two malicious releases of Microsoft’s Python agent-framework package appeared on PyPI on November 17, 2026. Versions 1.26.1 and 1.26.2 installed startup hooks that could run whenever Python started in an affected environment—even if the application never imported the framework. The incident put cloud and CI credentials accessible to those environments at risk.
3
32
What happened
Version 1.26.1 was published at 20:35 UTC, followed by 1.26.2 at about 21:08 UTC. Reports describe the releases as wheel-only uploads.
28
32
Aikido identified an exposure window beginning at 20:35 UTC and ending around 21:20 UTC; other reporting puts the versions’ disappearance from PyPI at about 21:30 UTC. The exact cutoff therefore varies across reports. An installation could also happen indirectly if a project used a loose dependency requirement such as agent-framework>=1.26.
38
7
The package had roughly 190,000 monthly downloads according to one report. That figure indicates the package’s reach, not how many people installed the malicious versions or had credentials stolen.
6
How the credential stealer worked
The releases added .pth files—Python startup files that can run code when an interpreter starts. Researchers reported that the malicious code gathered cloud and CI/CD credentials and sent collected data to a webhook.site endpoint. Because execution happened at startup, importing agent-framework was not required.
32
38
The reports identify Azure, Azure DevOps, and GitHub Actions credentials among the potential targets. Exposure depended on what secrets and identity tokens were available to the affected process; the available reporting does not establish that every installation resulted in stolen credentials.
3
5
The second malicious upload followed the first by about 33 minutes, showing that someone was able to publish another compromised version at that time. The available sources do not establish the root cause of the publishing access or whether it remained compromised after the incident was contained.
32
17
What affected users should do
If agent-framework 1.26.1 or 1.26.2 was installed in a workstation, build runner, container, or other environment during the reported window:
- Check dependency files and build records. Look for either affected version, including installations resolved from a loose requirement such as
agent-framework>=1.26.
38
- Rebuild affected environments from clean dependencies. Remove the compromised package and startup hook, then recreate virtual environments, runners, or images rather than relying on uninstalling alone.
10
38
- Rotate accessible secrets. Revoke or replace credentials and tokens the affected process could access, including secrets provided to CI jobs. Treat them as potentially exposed even if there is no evidence they were actually used by an attacker.
3
11
- Pin to the last clean release identified in the reports. The sources identify
agent-framework==1.26.0 as the last clean version.
13
28
Removing the package or its startup hook can stop future execution, but it cannot undo credentials that may already have been collected. Rebuilding the environment and rotating secrets address different parts of the response.
10
What remains uncertain
The supplied reporting gives different estimates for when the malicious versions stopped being available, ranging from about 21:20 to 21:30 UTC. It also does not establish the incident’s root cause or whether publishing access remained compromised after the malicious releases were removed or quarantined. Treat those points as unresolved rather than assuming a precise end time or cause.
7
38
13