NewApp Monitoring is liveSign up free
AgentbeamBeta
Beam · Attacks tracker

November 2026 attacks tracker

Every supply chain compromise, breach, exploited vulnerability, AI-run attack and agent incident of November 2026 we could verify, newest first. Each entry has its status and a link to a full breakdown with primary sources. Link to any incident, filter by type, or embed one on your own site.

Checked every 4 hours · last updated Nov 4, 2026, 10:01 UTC · 8 incidents · Read the month as one article

Share on XLinkedInBluesky
Supply chain
0
Breach
4
Exploited
1
Critical vuln
0
AI-run attack
1
Agent incident
2

November incidents

Date is when the attack happened, or when it was first disclosed if that is all that is known.

8 incidents in November 2026

Week 1 · November 1 to 7

  1. Agent incidentConfirmed (Check Point)

    Haiou Codex jailbreak bundle plants ads in agent instructions

    Check Point Research analysed Haiou 4.5.0, a Codex jailbreak bundle that rewrites the agent's global instructions so greetings trigger an ad for a third-party LLM gateway.

    Full breakdown →Share on XLinkedIn
  2. BreachConfirmed (SpyCloud)

    WardenStealer and Aoki infostealers take Claude Code and Codex tokens

    SpyCloud analysed recovered infection logs from the Windows infostealers WardenStealer and Aoki and found Claude Code and Codex credential files (OAuth tokens, API keys) collected; a password reset does not revoke them.

    Full breakdown →Share on XLinkedIn
  3. ExploitedPatched

    WordPress Core upgrade-window RCE (CVE-2026-119977) added to CISA KEV

    CISA added CVE-2026-119977, a TOCTOU flaw in WordPress Core's upgrade staging paths (4.7 through 7.1.3) allowing unauthenticated code execution during an upgrade, to KEV on Nov 3. Fixed in 7.1.4 (Oct 28); federal due date Nov 6.

    Source →Share on XLinkedIn
  4. Agent incidentPartly confirmed (Railway apology); details one-sided

    Primcloud says a Railway engineer's AI agents probed its infrastructure

    Primcloud's founder says AI agents run by a Railway engineer scanned its network and requested secrets; he says every attempt was blocked. Railway's CEO apologized, said the activity looked agent-driven, and will ban non-manual external testing. No logs are public.

    Full breakdown →Share on XLinkedIn
  5. AI-run attackConfirmed

    CyberStrikeAI: LLM on the C2 server takes over education domains

    Kaspersky says the open-source CyberStrikeAI framework put an LLM orchestrator on the C2 server to run post-exploitation against education networks in Africa and Latin America, reaching domain admin in 3-4 days.

    Full breakdown →Share on XLinkedIn
  6. BreachConfirmed (GitBook); AI-agent detail unverified

    GitBook: AI-agent attack reaches infrastructure credentials

    GitBook says a targeted attack using AI agents accessed some infrastructure credentials on Nov 2. Integration tokens, Git Sync secrets, API tokens and Assistant questions may be exposed; all personal API tokens revoked, MCP server needs re-authentication. No content changes found.

    Full breakdown →Share on XLinkedIn
  7. BreachReported (Northflank)

    Northflank security incident: control-plane secrets, AI key misuse

    Northflank told all customers to rotate integration and project secrets after an attack on secrets in its control plane; some customers reported unauthorized AI key use. Running workloads were not affected, per the company. Root cause not yet published.

    Full breakdown →Share on XLinkedIn
  8. BreachConfirmed (WorkOS); ARTEX link unverified

    WorkOS: internal sales app accessed, CEO links attack to ARTEX

    WorkOS says an internal sales app was accessed without authorization (detected Oct 30), exposing CRM data and customer Slack excerpts; production services not affected, per the company. The ARTEX link comes from the CEO, not the bulletin.

    Full breakdown →Share on XLinkedIn

Reported in November, started earlier

Disclosed or covered this month, but the attack or fix predates November.

Unconfirmed claims

Kept apart from confirmed incidents. A claim moves into the tracker once the company or a named research team confirms it.

Embed an incident

Every entry has its own card you can put on a blog post, wiki page or internal dashboard. Click Embed under any incident to copy its code.

The card shows the date, type, status and summary, and links back to the full breakdown. It updates by itself when the entry changes, for example when a claim is confirmed or a fix ships.

Cards follow the reader’s light or dark setting. Add ?theme=dark or ?theme=light to the iframe address to fix one.

Free to use with the attribution line included in the code.

How the tracker works

Beam’s blog bot checks security advisories, vendor disclosures, research write-ups and security news every 4 hours and adds each new incident it can verify. A new tracker starts on the first of every month, with a matching November 2026 attacks timeline on the blog.

Supply chain
A package, release, plugin or update channel shipped malicious code
Breach
A company's systems or customer data were accessed
Exploited
A vulnerability with confirmed in-the-wild attacks
Critical vuln
A severe flaw disclosed and patched, with no confirmed exploitation yet
AI-run attack
An intrusion where agents or LLMs did substantial operational work
Agent incident
An AI agent caused harm or broke a control without an outside attacker

Confirmed means the affected company, a government agency or a named research team stated it. Reported means one vendor’s research that has not been independently corroborated. Unconfirmed claims stay in their own list.

Spotted an error or a missing incident? Tell us.

Other months