Hackers Publish Malicious Microsoft Agent Framework Packages

Two tainted versions of a Microsoft AI package on PyPI carried a credential stealer that could run on normal Python startup.

Updated on Nov. 18, 2026 in Cybersecurity

Vector editorial illustration of a clear glass vial with a dark teal core, cracked along its side with a small oxblood stain spreading across a cream surface.
Two tainted Microsoft agent-framework packages uploaded to PyPI on November 17 carried a credential stealer that ran on ordinary Python startup before both versions were removed. AI Illustration. Upload story photo >

Live Poll

Do you trust software packages you download to be free of malicious code?

Hackers published malicious versions 1.26.1 and 1.26.2 of Microsoft's agent-framework package on PyPI on November 17, 2026. The releases contained a credential stealer that targeted Azure identities, GitHub credentials and build secrets, and both were removed from PyPI by 21:30 UTC.

Why it matters

The package has about 41,000 normal downloads per week, and the stealer runs even if an application never imports Agent Framework, so any developer environment that installed the affected versions may be exposed. The attack shows how a trusted, legitimately published package can carry malicious code that is hard to detect through normal review.

Both malicious releases placed a .pth file in site-packages, which Python executes during normal startup, and version 1.26.2 moved the payload into af_runtime_diag.py, triggered by af_runtime_diag.pth. Wiz found no matching python-1.26.1 tag or release in Microsoft's GitHub repository and no malicious code on its main branch.

The players

Microsoft

Microsoft is a multinational technology company that develops the Azure cloud platform, GitHub, and the agent-framework package at the center of this incident.

Wiz

Wiz is a cloud security company whose researchers traced the malicious uploads and analyzed the credential stealer in the affected releases.

PyPI

The Python Package Index is the central public repository from which Python developers download packages, and it is where the malicious versions were published.

The details

Wiz traced the first upload to 20:35 UTC and the second to about 21:08 UTC, and the releases were published under the legitimate Microsoft-associated PyPI publisher. The credential stealer was designed to run during ordinary Python startup rather than only when the package was imported.

Timeline

  1. November 17, 2026: Hackers publish malicious versions 1.26.1 and 1.26.2 on PyPI.

  2. 20:35 UTC, November 17, 2026: Wiz traces the first malicious upload.

  3. About 21:08 UTC, November 17, 2026: Wiz traces the second malicious upload.

  4. 21:30 UTC, November 17, 2026: Both malicious versions are no longer available on PyPI.

The Tech Race

The incident follows a documented pattern of software supply-chain attacks on public package registries like PyPI and npm, in which attackers exploit trust in legitimately published packages. It shows that the same trust developers place in major vendors' packages can become the delivery route for credential theft.

Developers who installed agent-framework versions 1.26.1 or 1.26.2 should check their environments and treat any Azure identities, GitHub credentials or build secrets on those systems as potentially exposed. Reverting to the latest known clean release, 1.26.0, is the verified safe baseline cited by Wiz.

The takeaway

Developers should pin dependency versions and verify package releases against a project's official source repository before installing updates. Treating every install as a potential code-execution event is now a practical baseline for protecting credentials.

Further reading

Explore more Cybersecurity coverage to see how software supply-chain threats are tracked across the industry.

Live Poll

Do you trust software packages you download to be free of malicious code?