agent-framework PyPI Malware: Microsoft Package Versions 1.26.1 and 1.26.2 Carried a Credential Stealer, and What to Rotate This Week
Two malicious versions of Microsoft's agent-framework package, 1.26.1 and 1.26.2, were published to PyPI on November 17, 2026 with a stealer aimed at Azure, GitHub Actions and CI/CD credentials. Here is how to check and what to rotate.
Where Worldwide
On this page 9 sections
Two malicious versions of Microsoft's agent-framework Python package, 1.26.1 and 1.26.2, were published to PyPI on Tuesday, November 17, 2026. They carried a credential stealer aimed at Azure, Azure DevOps, GitHub Actions and CI/CD secrets. If a developer laptop, build server or pipeline in your company installed either version, treat the credentials on that machine as exposed and rotate them this week.
The bad versions were only up for a short time, under an hour by the researchers' timeline. But the package is popular, and the machines that install developer packages are usually the ones that hold the keys to your cloud.
What happened to agent-framework on PyPI
PyPI is the public index where Python developers download open source libraries. Researchers at Wiz and Socket both reported that two versions of the Microsoft agent-framework package published there were malicious. Socket put it this way: "The Microsoft agent-framework PyPI package was compromised on November 17th, affecting versions 1.26.1 and 1.26.2."
Wiz published this timeline:
| Time (UTC, November 17, 2026) | What happened |
|---|---|
| 20:35 | Malicious version 1.26.1 published to PyPI |
| 21:08 | Second malicious version, 1.26.2, published |
| 21:30 | Both versions no longer available on PyPI |
Wiz also notes that the package normally gets almost 200k downloads a month. That figure covers the package overall. It does not count downloads of the malicious versions.
What the agent-framework credential stealer targets
The two research firms describe the targets in slightly different words:
- Socket: the malicious versions were built to exfiltrate Azure, GitHub Actions and CI/CD credentials.
- Wiz: "The stealer is focused on Azure and Azure DevOps."
Put together, the stealer goes after the credentials that let someone reach your Azure cloud account, your Azure DevOps projects, and the automated pipelines that build and deploy your code.
What is confirmed and what is not known
Confirmed by the researchers' own reports:
- Versions 1.26.1 and 1.26.2 of agent-framework on PyPI were malicious.
- They were published on November 17, 2026, at 20:35 and 21:08 UTC.
- Both were no longer available on PyPI as of 21:30 UTC.
- The code targets Azure, Azure DevOps, GitHub Actions and CI/CD credentials.
- Wiz says: "The most recent safe version is 1.26.0."
Not known from the sources we used:
- How the attackers were able to publish under the agent-framework package name.
- How many times 1.26.1 or 1.26.2 were downloaded or installed.
- Whether any stolen credentials have been used against anyone.
- What Microsoft has said. This post relies on the two research firms, not on a Microsoft statement.
We will not fill those gaps with guesses. If you see claims that specific companies had credentials stolen, ask for the source.
Who is affected by the agent-framework compromise
You are only at risk if version 1.26.1 or 1.26.2 was actually installed somewhere. In practice that means one of these:
- A developer ran an install or upgrade of agent-framework on November 17 without pinning a version.
- A CI/CD pipeline, such as GitHub Actions or Azure DevOps, built a project that pulls agent-framework without a fixed version.
- A container image was built during that window and still contains the bad version.
- Your company runs an internal package mirror or proxy that saved a copy. Removal from PyPI does not remove a copy you already stored.
If every project pins agent-framework to 1.26.0 or earlier and nothing pulled a newer version, these two releases did not reach you.
How to check if you installed agent-framework 1.26.1 or 1.26.2
On each machine or build environment that uses Python:
- Run
pip show agent-frameworkand look at the Version line. - Search your lockfiles and requirements files (
requirements.txt,poetry.lock,uv.lock,Pipfile.lock) for1.26.1or1.26.2. - Check CI/CD build logs from November 17, 2026 for installs of agent-framework, especially runs from 20:35 UTC onward.
- Check any container images built on or after November 17 that include Python dependencies.
- If you run an internal package mirror, search it for either version and delete them.
What to do this week
| Step | Action |
|---|---|
| 1. Find it | Use the checks above on laptops, build servers, pipelines and images |
| 2. Remove it | Uninstall 1.26.1 or 1.26.2 wherever you find them |
| 3. Pin the safe version | Install agent-framework==1.26.0, which Wiz names as the most recent safe version |
| 4. Rotate Azure credentials | Replace any Azure and Azure DevOps credentials that were on, or reachable from, an affected machine |
| 5. Rotate pipeline secrets | Replace GitHub Actions secrets and other CI/CD secrets that the affected pipeline could read |
| 6. Review activity | Look through Azure, Azure DevOps and GitHub activity since November 17 for logins, deployments or changes nobody on your team made |
Socket's advice is short: "if installed, remove them and rotate potentially exposed credentials." The order matters. Removing the package stops it from running again, but if the stealer already ran, whatever it read may already be gone. Rotating the credentials is what closes that door.
Why this matters for a business network or website
This was not a flaw in software you bought. It was a trusted package name serving malicious code through the normal install process. Nobody had to click a phishing link. A routine upgrade was enough.
The machines that install packages like this are developer laptops and build pipelines. Those machines often hold the credentials that deploy your website, reach your databases and manage your cloud account. A stolen Azure or CI/CD credential can be worth more to an attacker than any single laptop.
It also shows why always running the latest version is not a complete policy. In this case, anyone who upgraded on November 17 got the malicious release, and anyone who stayed on 1.26.0 did not. We wrote about the gap between updating and actually being safe in Updated Is Not the Same as Patched.
If your team or an outside developer is adding AI libraries to your products, someone needs to own the dependencies once the code ships. That is the subject of AI Can Build Your App. Who Is Going to Keep It Running? and Who Is Patching the Software That Runs Your Business?. If you host your own build servers, our self-hosting and infrastructure page covers how we set them up.
agent-framework PyPI compromise questions people are asking
Which agent-framework versions are malicious?
Versions 1.26.1 and 1.26.2 on PyPI, both published on November 17, 2026.
What is the safe version of agent-framework?
Wiz names 1.26.0 as the most recent safe version.
Are the malicious versions still on PyPI?
No. Wiz reports that both were no longer available on PyPI as of 21:30 UTC on November 17, 2026. Copies saved in private mirrors or container images can still exist.
What credentials does the stealer go after?
Azure, Azure DevOps, GitHub Actions and CI/CD credentials, according to Wiz and Socket.
I installed 1.26.1 or 1.26.2. Is uninstalling enough?
No. Remove it, pin 1.26.0, and rotate any credentials the affected machine or pipeline could reach.
Was Microsoft hacked?
The researchers describe the PyPI package as compromised. The sources we used do not say how the attackers got publishing access, so that is not known.
How many people downloaded the malicious versions?
Not known. The package normally gets almost 200k downloads a month, but that number is not a count of malicious installs.
Does this affect me if my company does not write Python?
Only if a vendor, contractor or internal tool installed agent-framework 1.26.1 or 1.26.2. Ask whoever builds your software to check.
The bigger lesson
Your software is only as trustworthy as the packages it pulls in at build time, and the build machines often hold your most powerful keys. Pin dependency versions, know which machines hold cloud and pipeline credentials, and make sure someone is responsible for acting the same day a package is reported compromised.
For help locking down your builds and cloud credentials, see security hardening or request a quote.
Get security alerts like this by email, plus our free checklist, at security alerts.
Sources: Wiz: Malicious version of Microsoft's agent-framework published to PyPI; Socket: agent-framework PyPI package compromised with credential stealer.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Automated AI Cyberattack: Google Finds exploit_agent Turning Software Patches Into Live Attacks With No Human in the Loop, and What to Do This Week
Google says attackers used an AI framework called exploit_agent to find and exploit flaws in popular web softw...
SignDrop Windows Zero-Day: Public Exploit Claims SYSTEM Access Through CLFS, No Microsoft Patch or CVE Yet, and What to Do This Week
A researcher has published SignDrop, exploit code they say turns a normal Windows login into full SYSTEM contr...
TSMC Data Breach: 46,000 Employee Records Reportedly for Sale, TSMC Finds No Evidence Its Systems Were Hit, and What to Check at Your Own Vendors
Anonymous sellers reportedly offered 46,000 TSMC employee records for three Bitcoins. TSMC says it found no ev...