Renovate Opened the Upgrade PR in Six Minutes: Microsoft's Poisoned agent-framework Shows Auto-Updates Now Race the Attacker

2026-11-19 · By H.A

Renovate Opened the Upgrade PR in Six Minutes: Microsoft's Poisoned agent-framework Shows Auto-Updates Now Race the Attacker

Renovate Opened the Upgrade PR in Six Minutes: Microsoft's Poisoned agent-framework Shows Auto-Updates Now Race the Attacker

Two malicious releases of Microsoft's agent-framework stayed on PyPI for about 40 minutes, yet bots had already started pulling them in, which shows that a trusted publisher name and fast dependency automation are now the attacker's delivery system.

What happened, briefly

On 17 November, two releases of Microsoft's official agent-framework Python package showed up on PyPI that never came from Microsoft's source repository. Version 1.26.1 was published at 00:35 Mauritius time on 18 November (20:35 UTC on 17 November), and version 1.26.2 followed at 01:08 Mauritius time (21:08 UTC). According to the GitHub Advisory Database entry GHSA-764m-3ppc-5m73, both carry a credential stealer that is not in 1.26.0, the last clean release. Both have since been removed.

The package gets roughly 190,000 downloads a month. It is the Python entry point for Microsoft's framework for building AI agents. Those are exactly the environments that tend to hold cloud credentials, LLM API keys and CI tokens at the same time.

The technical write-ups have already covered the mechanics in detail. This piece is about what the timeline tells us, because the timeline is the uncomfortable part.

The 40-minute window was long enough

Researchers who rebuilt the timeline say Renovate bots were opening upgrade pull requests in downstream repositories within six minutes of 1.26.1 appearing. PyPI quarantined 1.26.1 at 01:06 Mauritius time (21:06 UTC). Two minutes later, 1.26.2 was live. Both were gone by about 01:16 Mauritius time (21:16 UTC).

There are two lessons here.

"Never imported, still ran"

The payload's delivery choice matters for defenders. Each malicious wheel drops a .pth file into the root of site-packages: agent_framework_meta.pth in 1.26.1 and af_runtime_diag.pth in 1.26.2. Python processes .pth files every time the interpreter starts, so the stealer runs whenever Python starts in that environment. That includes a test runner, a linter, a notebook kernel, or pip itself. Nobody has to import the framework.

The stealer forks into the background and stays quiet about errors. It collects environment variables whose names match patterns such as TOKEN, SECRET, KEY, AZURE, AWS, GITHUB and OPENAI, plus secrets it finds in other processes' environments. It also reads credential files such as Azure CLI caches, .npmrc, .netrc, .git-credentials and Docker configs, along with .env files in container paths. On Azure hosts it asks the instance metadata service for managed-identity tokens covering Resource Manager, Key Vault, Storage, Graph and Azure DevOps. Version 1.26.2 added GitHub Actions OIDC tokens. Everything is compressed, base64-encoded and sent in one POST to a webhook[.]site URL.

The real framework code is still there, so applications keep working. That is why "the build passed" tells you nothing.

The odd detail: a free-tier webhook capped the damage

One research team analysed the exfiltration endpoint and found it was on a free tier that accepted only a limited number of requests. Of the 50 captured requests, they attribute 4 to the attacker's own testing and 29 to sandboxes and security scanners. The remaining 17 represent just three unique, successful thefts of victim data.

Read that carefully. It does not mean only three organisations were affected. Once the cap was reached, later sends would have failed silently, so the true number cannot be known from the webhook alone. What it does show is that the damage was limited by the attacker's own sloppy infrastructure, not by any defensive control. The next attacker will pay for a proper endpoint.

How did it get published? Nobody knows yet

This is where the facts are thin, and it is worth being honest about that.

A framework maintainer has acknowledged the incident in a GitHub discussion and said an investigation is under way. Microsoft has not yet published a root cause. Until it does, treat every explanation above as provisional.

The bigger point: the publisher name was the exploit

Most PyPI malware relies on typosquats and look-alike names that careful teams have learned to catch. This attack needed none of that. It came under the right name, from the right publisher, with a plausible patch-level version bump. Every control that asks "is this the real package?" said yes.

AI agent frameworks make this worse in a structural way. An agent runtime is designed to hold the keys to many systems at once: model providers, vector databases, cloud resources and source control. Compromising one dependency in that stack is a very efficient way to collect credentials.

Practical takeaways

# Look for the malicious hooks WITHOUT starting Python in a suspect environment
find / -path /proc -prune -o \( -name 'agent_framework_meta.pth' -o -name 'af_runtime_diag.pth' -o -name 'af_runtime_diag.py' \) -print 2>/dev/null
# Search lockfiles in your repositories for the bad versions
grep -rnE 'agent[-_]framework[^-]*(==|@ ?)1\.26\.[12]\b' --include='*.txt' --include='*.lock' --include='pyproject.toml' .

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.