Skip to content
TrustList
Security advisories

Malicious agent-framework releases on PyPI steal cloud and CI credentials

Editorial

By TrustList Editorial

Versions 1.26.1 and 1.26.2 of the agent-framework package on PyPI, published on 17 November 2026 and since removed, carried a credential stealer that ran at every Python start; anyone who installed them should rotate their secrets.

About Malicious agent-framework releases on PyPI steal cloud and CI credentials

Malicious agent-framework releases on PyPI steal cloud and CI credentials

18 November 2026: Two releases of agent-framework, the Python package for Microsoft Agent Framework, contained a credential stealer, according to a malware advisory published in the GitHub Advisory Database. Versions 1.26.1 and 1.26.2 were both published to PyPI on 17 November, at 20:35 and 21:08 UTC, and have since been removed. The last clean release is 1.26.0. Python teams building AI agents are the ones most likely to have pulled the package that evening.

Not yet independently verified. The details are from the GitHub Advisory Database entry GHSA-764m-3ppc-5m73, published on 18 November 2026 as a malware advisory. We found no statement from Microsoft, whose Agent Framework the package is, and it is not yet known how the malicious releases were published. We will update this when it can be confirmed, and remove this note.

How it ran

Each malicious wheel added a .pth file, a kind of startup hook that Python reads every time an interpreter starts. That means the code ran as soon as the package was installed and Python was next started, without anyone importing agent_framework. In 1.26.1 the files were named agent_framework_meta.pth and _telemetry.py; in 1.26.2 they were renamed af_runtime_diag.pth and af_runtime_diag.py. The helper detached into a background process and hid its errors. The rest of each wheel matched 1.26.0.

What it took

The advisory lists what the stealer collected:

  • environment variables whose names contain TOKEN, SECRET, PASSWORD, KEY, AZURE, AWS, GITHUB, HF_, OPENAI, NPM, PIP or CI_, and the environments of other running processes;
  • credential files including ~/.azure, .npmrc, .netrc, .git-credentials, the Docker config, the Hugging Face token, Azure DevOps agent credentials and .env files;
  • Azure DevOps OIDC tokens and Azure managed identity tokens from the instance metadata service;
  • in 1.26.2, GitHub Actions OIDC and runtime tokens as well.

The data was compressed, encoded and sent by HTTP POST to an address on webhook.site. The advisory gives the SHA-256 hashes of both wheels so teams can search their caches and artefact stores.

Find the two versions and rotate secrets

Search lock files, build logs, container images and package caches for agent-framework 1.26.1 or 1.26.2, and for the four .pth and helper file names above in site-packages. Pin the package to 1.26.0 or a later release you have checked.

If either version was installed anywhere, on a laptop, a build agent or a server, treat every secret reachable from that environment as exposed. Rotate cloud keys, Azure service principals and managed identity permissions, GitHub and Azure DevOps tokens, CI secrets, package registry tokens and model provider API keys, then review cloud and repository audit logs from 17 November for activity you do not recognise. For the longer term, install Python packages in CI from a pinned lock file with hashes, and consider a short delay before new releases of dependencies are allowed into builds.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in