Wiz reported on November 18, 2026, that 17 of 50 retained requests it analyzed corresponded to three unique cases of successful victim-data exfiltration. The finding concerns that request sample, not a total count of affected installations or organizations. The requests were tied to malicious releases 1.26.1 and 1.26.2 of Microsoft’s agent-framework package on PyPI, published the previous day.

If an environment may be affected, isolate it before starting Python or pip to inspect it.

What Wiz’s request analysis found

The 17 requests represented three unique cases in Wiz’s analysis of 50 retained requests. StepSecurity cautioned that a connection to the reported destination alone does not establish that data was successfully transferred. That distinction matters when teams review network logs: a connection is a lead to investigate, while Wiz’s three cases were identified as successful exfiltration.

How the two releases ran without an import

Taistek explains how Python .pth startup hooks can run without an explicit package import and discusses incident-response concepts.

The reported malicious releases were limited to versions 1.26.1 and 1.26.2 of the agent-framework PyPI package. Their .pth files contained import lines that Python processes during startup in an affected environment, so an application did not need to import Microsoft Agent Framework to trigger the reported code.

Wiz identified the startup files as agent_framework_meta.pth in version 1.26.1 and af_runtime_diag.pth in version 1.26.2. Its analysis said the payload sought environment variables, credential files, other processes’ environment data, Azure DevOps OIDC tokens, managed-identity tokens and instance metadata. Version 1.26.2 also sought GitHub Actions OIDC tokens; whether a token could be issued depended on workflow permissions and identity trust configuration.

Wiz said the payload attempted to send collected material to a hard-coded webhook.site endpoint in a compressed, Base64-encoded HTTPS request. The collection targets describe what the code sought, not proof that every token was issued or every item transferred.

Isolate the environment before starting Python or pip

StepSecurity recommends isolating a potentially affected host, container or runner before invoking Python or pip. Starting either in that environment can process the startup hook again. Then preserve logs and process information with trusted tooling, stop any identified collector, and rebuild from a known-clean base. Removing a .pth file alone may not stop a detached collector that is already running.

After containment, assess and rotate credentials the payload could read or request, and review identity access. This includes credentials available to the environment and cloud or CI identities whose permissions could allow token issuance.

The second release followed the first quarantine

StepSecurity reported that PyPI quarantined version 1.26.1 at 21:06:16 UTC on November 17, 2026. Version 1.26.2 was uploaded at 21:08:39 UTC, 2 minutes and 23 seconds later, and was quarantined at 21:16:44 UTC. The first quarantine therefore preceded, but did not prevent, the second reported upload.

In its November 18 update, Wiz attributed the publishing activity to an apparent compromise of a Microsoft ESRP client certificate and private key. Wiz said how those credentials were obtained was not known.