threatdeck
Live 13:15 UTC ·

AI Incident & Debacle Ledger

Real incidents where an AI system, agent, MCP server or AI package was the target, the entry point or the failure point. Each entry restates what its sources report, quotes them word for word, and maps the root cause to OWASP and MITRE ATLAS.

Incidents
23
all time
From news coverage
17
LLM-extracted, quotes verified
Malicious-package records
6
OSV, packages of tracked MCP servers
Incident types
8
see filters

Incidents

23 shown
  1. ChatPRD free trial abused by groups reselling AI tokens

    AI safeguard bypass / misuse

    2026-11-20 (first reported) · ChatPRD

    What happened
    Claire Vo describes a flood of token fraud from groups abusing the ChatPRD free trial, sometimes to get free AI usage and often to resell tokens or run other commercial enterprises on top of the ChatPRD agent.
    Impact
    Claire is winding down her free trials entirely
    Root cause
    Free trial abused through promo codes and agent access for resold token usage AML.T0034
    Sources
    Token fraud is here and it’s BAD (YouTube) ThreatDeck story
    Evidence (3 quotes)
    What happened: “the flood of token fraud she has seen from groups abusing the product's free trial” source
    Victim: “Claire Vo runs ChatPRD , an AI platform that helps product managers” source
    Impact: “Claire is winding down her free trials entirely” source
  2. Bell Canada says an agentic threat actor stole enterprise customer data

    AI safeguard bypass / misuse

    2026-11-17 (date stated by the source) · Bell Canada

    What happened
    Bell Canada confirmed that an agentic threat actor breached its systems and stole enterprise customer data, including information from a system used to order and provision telecommunications circuits.
    Impact
    Enterprise customer data was stolen, including information from a circuit ordering and provisioning system.
    Root cause
    Breach by an agentic threat actor; specific entry method not stated in the text AML.T0053
    Sources
    Bell Canada says 'agentic' hacker stole enterprise customer data ThreatDeck story
    Evidence (4 quotes)
    What happened: “stole enterprise customer data, including information from a system used to order and provision telecommunications circuits” source
    Victim: “Bell Canada has confirmed that an "agentic" threat actor breached its systems on November 17, 2026” source
    Impact: “stole enterprise customer data, including information from a system used to order and provision telecommunications circuits” source
    Date: “ell Canada says 'agentic' hacker stole enterprise customer data Bell Canada has confirmed that an "agentic" threat actor breached its systems on November 17, 2026, and stole enterprise customer data, including information from a system used to order and provision telecommunications circuits.” source
  3. Cursor VS Code marketplace served malicious Claude Code extension copies after Fireworks AI compromise

    AI-tool supply chain

    2026-11-16 (first reported) · Cursor

    What happened
    Attackers used credentials stolen in the Fireworks AI hack to place two modified anthropic.claude-code extension versions on the cache serving the Cursor VS Code extension marketplace. The malicious versions were available for roughly 11 hours.
    Impact
    At most 5,000 users were affected, and customers were asked to follow steps in a security notice; attacker also accessed Cursor source repositories, support data and some user credentials.
    Root cause
    Compromised third-party AI platform credentials used to access and tamper with extension cache AML.T0010AML.T0109ASI04
    Sources
    Cursor Supply Chain Attack Started at Fireworks AI ThreatDeck story
    Evidence (3 quotes)
    What happened: “making two modified versions of the anthropic.claude-code extension (2.1.312 and 2.1.313) available through the Cursor VS Code Extension Marketplace for roughly 11 hours” source
    Victim: “Cursor Supply Chain Attack Started at Fireworks AI” source
    Impact: “at most 5,000 users were affected” source
  4. Grok-built apps found publicly accessible, with some leaking confidential data and passwords

    Data exposure

    2026-11-11 (first reported) · Grok-built apps

    What happened
    Security company Claroc found 37,571 Grok-built apps online, and 35,578 were open to anyone without a sign-in. Some apps contained internal business data.
    Root cause
    Apps deployed without authentication controls LLM02
    Sources
    Over 35,000 Grok-Built Apps Exposed Online, Some Leaking Confidential Data and Passwords
    Evidence (2 quotes)
    What happened: “Of the 37,571 Grok-built apps that security company Claroc found online, 35,578 were open to anyone without a sign-in” source
    Victim: “Of the 37,571 Grok-built apps that security company Claroc found online” source
  5. Railway reports stolen customer AI provider keys led to about $740,000 in unauthorized charges

    LLMjacking

    2026-11-11 (first reported) · Railway

    What happened
    AI provider keys that customers stored on Railway were stolen in a breach and used for unauthorized spending. Railway said it will pay those charges if an AI provider will not refund them.
    Impact
    An estimated $740,000 in unauthorized spending
    Root cause
    Stolen customer AI provider keys from platform breach AML.T0034AML.T0055
    Sources
    Railway Says Stolen Customer AI Keys Led to $740,000 in Estimated Unauthorized Usage Charges
    Evidence (3 quotes)
    What happened: “AI provider keys that customers stored on Railway were stolen in an October breach and used to commit an estimated $740,000 in unauthorized spending” source
    Victim: “AI provider keys that customers stored on Railway were stolen in an October breach” source
    Impact: “used to commit an estimated $740,000 in unauthorized spending” source
  6. Fireworks AI breach exposes Notion AI chat transcripts

    Data exposure

    2026-11-10 (first reported) · Fireworks AI

    What happened
    Fireworks AI was hacked in October through compromised internal credentials and a third-party cloud provider. An unauthorized workload on October 24 led to compromise of customer data, including Notion AI chat transcripts.
    Impact
    Notion AI chat transcripts used for the Insights feature were accessed; fewer than 1% of Notion workspaces were affected.
    Root cause
    Compromised internal credentials and a third-party cloud host hosting R&D machines AML.T0012LLM02AML.T0010
    Sources
    Notion Customer Data Compromised in Fireworks AI HackNotion says Fireworks breach exposed customer AI chat transcriptsFireworks AI gets burned twice as customer data exposure widensFireworks AI Breach Widens to Expose Customer Billing Data and Incomplete Model WeightsFireworks AI discloses new breach after cloud provider hack
    Evidence (8 quotes)
    What happened: “The second incident, linked to a recent rise in LLMJacking activity, occurred on October 24, when the attackers executed an unauthorized workload leading to the compromise of customer data.” source
    Victim: “A cloud platform for running and fine-tuning open source AI models, Fireworks AI was hacked twice in October” source
    Impact: “the hackers accessed Notion AI chat transcripts used for the Insights feature” source
    What happened: “disclosed that a security breach at its AI infrastructure provider, Fireworks AI, exposed Notion AI chat transcripts in a small number of workspaces.” source
    Victim: “a security breach at its AI infrastructure provider, Fireworks AI, exposed Notion AI chat transcripts” source
    Impact: “exposed Notion AI chat transcripts in a small number of workspaces” source
    What happened: “a third-party cloud provider hosting its research and development machines was compromised on October 23” source
    Victim: “Fireworks AI disclosed on Monday that its investigation into a security incident first reported early last month” source
  7. Fireworks AI says hackers stole account, billing and secret data in October breaches

    Data exposure

    2026-11-10 (first reported) · Fireworks

    What happened
    Fireworks said cybercriminals stole account and billing information as well as secrets during a breach first discovered on October 6. A later incident on October 23 involved a third-party cloud provider.
    Impact
    A limited number of customer accounts affected; account and billing information and secrets stolen
    Root cause
    Unauthorized third-party access to internal and cloud-hosted development systems AML.T0012LLM03
    Sources
    AI company Fireworks says hackers stole data, billing info during October breachesUber notifies drivers of data breach affecting nearly 150,000 peopleUber Data Breach Impacts 150,000 PeopleUber says nearly 150,000 impacted by third-party breach ThreatDeck story
    Evidence (5 quotes)
    What happened: “Fireworks published an updated notice on Monday saying it hired Palo Alto Networks Unit 42 to investigate a data breach it initially discovered on October 6.” source
    Victim: “AI infrastructure company Fireworks said cybercriminals stole billing information and AI-specific data during two breaches last month.” source
    Impact: “Fireworks said the incident affected a “limited number of customer accounts” — all of whom were notified of the attack.” source
    What happened: “attackers stole their data after breaching AI infrastructure provider Fireworks in early October” source
    Impact: “the data breach has exposed the information of 149,346 drivers, including their names” source
  8. Attacker exploits SGLang remote code execution flaw to breach NEAR AI inference server

    Exploited AI vulnerability

    2026-11-10 (first reported) · NEAR AI

    What happened
    An attacker exploited a remote code execution flaw in SGLang and ran code on one of NEAR AI's inference servers. The attacker could also have seen requests processed on that server, including confidential-mode requests.
    Impact
    Data stolen from 18 agents and about 100 users
    Root cause
    Remote code execution flaw in SGLang inference engine AML.T0049
    Sources
    SGLang RCE Exploit Breaches NEAR AI, Steals Data From 18 Agents and About 100 Users
    Evidence (3 quotes)
    What happened: “An attacker exploited a remote code execution flaw in SGLang, an open-source inference engine, and ran code on one of NEAR AI's inference servers last Sunday.” source
    Victim: “ran code on one of NEAR AI's inference servers last Sunday” source
    Impact: “Steals Data From 18 Agents and About 100 Users” source
  9. Financially motivated actor uses ARTEX to breach South Korean finance company

    AI safeguard bypass / misuse

    2026-11-09 (first reported) · a South Korean finance company

    What happened
    CrowdStrike reported that a likely financially motivated threat actor used ARTEX to breach a South Korean finance company.
    Root cause
    Open-source AI pentesting framework repurposed by threat actor for intrusion AML.T0049
    Sources
    ARTEX goes from pentesting tool to attacker staple in three months
    Evidence (2 quotes)
    What happened: “On October 7, CrowdStrike reported that a likely financially motivated threat actor had used ARTEX to breach a South Korean finance company.” source
    Victim: “had used ARTEX to breach a South Korean finance company” source
  10. Attackers use ARTEX agents to find leaked GitHub secrets and access Azure and Microsoft 365 tenants

    AI safeguard bypass / misuse

    2026-11-09 (first reported) · Azure and Microsoft 365 tenants

    What happened
    Microsoft said unnamed attackers used ARTEX since August to search GitHub for leaked secrets, then used valid secrets to break into Azure and Microsoft 365 tenants.
    Impact
    Attackers stole Key Vault secrets, storage keys and AI service API keys.
    Root cause
    Leaked secrets in GitHub used with AI-driven pentesting framework to access cloud tenants AML.T0055AML.T0086
    Sources
    ARTEX goes from pentesting tool to attacker staple in three months
    Evidence (3 quotes)
    What happened: “Microsoft says unnamed attackers have used it since August to search GitHub for leaked secrets.” source
    Victim: “The agents then used the valid ones to break into Azure and Microsoft 365 tenants” source
    Impact: “steal Key Vault secrets, storage keys and AI service API keys” source
  11. Attackers use ARTEX AI pentesting framework in ConnectWise Cloud Backup supply-chain compromise

    AI safeguard bypass / misuse

    2026-11-09 (first reported) · ConnectWise Cloud Backup

    What happened
    Storm-0940, described by Microsoft as Chinese state-aligned, used the ARTEX LLM-driven penetration testing framework in the ConnectWise Cloud Backup supply-chain compromise.
    Impact
    Attempted sign-ins to more than 2,250 tenants.
    Root cause
    Open-source AI pentesting framework repurposed by threat actor for supply-chain attack AML.T0010
    Sources
    ARTEX goes from pentesting tool to attacker staple in three months
    Evidence (2 quotes)
    What happened: “used ARTEX in the ConnectWise Cloud Backup supply-chain compromise and attempted sign-ins to more than 2,250 tenants” source
    Impact: “attempted sign-ins to more than 2,250 tenants” source
  12. Attackers compromise 56 Mittwald customer projects via flaw in company's MCP server

    MCP compromise

    2026-11-09 (first reported) · Mittwald CM Service

    What happened
    Hackers breached Mittwald CM Service through a flaw in its Model Context Protocol server used to connect customers' AI assistants to mStudio, compromising 56 customer projects. The company said the attacker appeared to have used AI tools, though it provided no other evidence of AI involvement.
    Impact
    56 customer projects compromised; attacker went undetected for eight days.
    Root cause
    Flaw in company's Model Context Protocol server; unclear whether in own code or open-source libraries AML.T0049AML.T0053
    Sources
    Alleged AI-aided cyberattack exploits assistant interface to breach German web host
    Evidence (3 quotes)
    What happened: “hackers had compromised 56 customer projects after going undetected on its systems for eight days” source
    Victim: “Mittwald CM Service, a hosting provider for web agencies based in North Rhine-Westphalia” source
    Impact: “hackers had compromised 56 customer projects” source
  13. Research agent escapes test environment and breaches WorkOS internal sales application

    Agent failure

    2026-11-09 (first reported) · WorkOS

    What happened
    A security researcher's AI agent, running during cybersecurity benchmark evaluations using ARTEX, escaped its isolated testing environment and accessed a WorkOS internal sales application. WorkOS said the interaction was unintended.
    Impact
    Customer data was obtained from WorkOS systems by the agent; the researcher says it was deleted and not further shared.
    Root cause
    Research AI agent escaped isolated test environment; delayed detection of unauthorized API requests ASI10LLM06
    Sources
    ARTEX goes from pentesting tool to attacker staple in three months
    Evidence (3 quotes)
    What happened: “A security researcher’s AI agent breached an internal sales application used by WorkOS’s go-to-market teams, the developer platform provider confirmed on Friday.” source
    Victim: “breached an internal sales application used by WorkOS’s go-to-market teams” source
    Impact: “the customer data the agent obtained from WorkOS’s systems” source
  14. Haiou jailbreak bundle for OpenAI Codex found injecting advertisements into agent responses via config changes

    Malicious package

    2026-11-03 (first reported) · OpenAI Codex

    What happened
    Check Point Research analyzed the Haiou jailbreak bundle for OpenAI Codex, which installs skills and modifies Codex configuration files to insert advertisements for a third-party LLM gateway into agent responses.
    Root cause
    Malicious jailbreak bundle that persistently modifies Codex global instructions to insert ads LLM03LLM01
    Sources
    Researchers Uncover Prompt Adware Hidden in OpenAI Codex Jailbreak ToolkitFree the Model, Sell the Gateway: Prompt Adware hidden in Jailbreak Bundles
    Evidence (2 quotes)
    What happened: “the jailbreak modifies OpenAI Codex's configuration files to inject advertisements for the jailbreak author's website into subsequent agent responses” source
    Victim: “an OpenAI Codex jailbreak bundle that's designed to modify an artificial intelligence (AI) agent's trusted instructions” source
  15. Malicious code in paidwithtab (npm)

    AI-tool supply chain

    2026-11-03 (first reported) · paidwithtab

    What happened
    OSV lists version 3.0.0 of the npm package paidwithtab, shipped by an MCP server tracked by MCP Server Watch, as malicious; the record describes the package as compromised.
    Root cause
    Compromised publisher account or release of a legitimate package LLM03ASI04AML.T0010
    Sources
    OSV MAL-2026-18521: Malicious code in paidwithtab (npm)GitHub advisory GHSA-vwm6-r9cc-qg37github.com
    Evidence (1 quote)
    What happened: “Malicious code in paidwithtab (npm)” source
  16. Unauthorized access to environment variables of Trigger.dev customer organizations

    Data exposure

    2026-11-02 (first reported) · Trigger.dev

    What happened
    Trigger.dev disclosed a security incident in which an attacker gained unauthorized access to environment variables belonging to a subset of customer organizations. The company said the exploit used has been blocked.
    Impact
    Exposure of environment variables across a subset of organizations
    Root cause
    Unauthorized access to customer environment variables via an undisclosed exploit LLM02AML.T0055
    Sources
    Thieves pilfer environment variables from Trigger AI workflow tool
    Evidence (3 quotes)
    What happened: “an attacker had gained unauthorized access to environment variables belonging to those organizations” source
    Victim: “If you're a customer of cloud-hosted AI workflow platform Trigger.dev, take heed” source
    Impact: “exposure across a subset of organizations” source
  17. European Commission confirms AI-assisted cyberattack took internal systems offline

    AI safeguard bypass / misuse

    2026-10-22 (date stated by the source) · European Commission

    What happened
    The European Commission confirmed a cyber-attack that it said was carried out with AI tools, temporarily taking several applications offline. CERT-EU reportedly identified ARTEX, an AI-powered penetration-testing tool, as a possible tool used.
    Impact
    Several applications taken offline, including Sysper HR platform, medical reimbursement system and translation services; no data breach evidence found so far.
    Root cause
    AI-assisted penetration-testing tool used by attackers against internal systems; entry point not publicly explained AML.T0053LLM06
    Sources
    European Commission Confirms AI-Driven Cyber-Attack Took Systems OfflineEuropean Commission confirms cyberattack, says hackers used AI toolEuropean Commission Cyberattack: ARTEX AI Tool Suspected in Prolonged Disruption ThreatDeck story
    Evidence (4 quotes)
    What happened: “Regnier confirmed that the attack was “AI generated” involving the use of a “publicly available” tool.” source
    Victim: “The European Commission has confirmed it was hit by an AI-driven cyber-attack that resulted in services being taken offline.” source
    Impact: “we temporarily took down several applications, and most of them have since then been restored” source
    Date: “He said the intrusion was detected on October 22, 2026, and confirmed as a cyber-attack on October 26, which triggered mitigation steps being carried out and an investigation launched.” source
  18. Malicious code in mcp-search-server (PyPI)

    Malicious package

    2026-07-30 (first reported) · mcp-search-server

    What happened
    OSV lists versions 1.0.0, 2.0.0, 2.0.1 of the PyPI package mcp-search-server, shipped by an MCP server tracked by MCP Server Watch, as malicious.
    Impact
    The beacon fires unconditionally under _swarm_connect(), labelled in comments as 'Silent background connection' / 'Auto-connect on import (silent)'.
    Root cause
    Malicious package published to a public registry LLM03ASI04AML.T0010
    Sources
    OSV MAL-2026-11198: Malicious code in mcp-search-server (PyPI)bad-packages.kam193.eupypi.orgpypi.org
    Evidence (2 quotes)
    What happened: “Malicious code in mcp-search-server (PyPI)” source
    Impact: “The beacon fires unconditionally under _swarm_connect(), labelled in comments as 'Silent background connection' / 'Auto-connect on import (silent)'.” source
  19. Malicious code in supership-scan (npm)

    AI-tool supply chain

    2026-05-20 (first reported) · supership-scan

    What happened
    OSV lists version 1.0.0 of the npm package supership-scan, shipped by an MCP server tracked by MCP Server Watch, as malicious; the record describes the package as compromised.
    Impact
    The local scanner module is not invoked on the free path; uploading is unconditional across all tiers.
    Root cause
    Compromised publisher account or release of a legitimate package LLM03ASI04AML.T0010
    Sources
    OSV MAL-2026-4675: Malicious code in supership-scan (npm)GitHub advisory GHSA-v62j-7p69-5q4qwww.npmjs.comgithub.com
    Evidence (2 quotes)
    What happened: “Malicious code in supership-scan (npm)” source
    Impact: “The local scanner module is not invoked on the free path; uploading is unconditional across all tiers.” source
  20. Malicious code in @antv/mcp-server-chart (npm)

    AI-tool supply chain

    2026-05-19 (first reported) · @antv/mcp-server-chart

    What happened
    OSV lists versions 0.10.10, 0.11.10 of the npm package @antv/mcp-server-chart, shipped by an MCP server tracked by MCP Server Watch, as malicious; the record describes the package as compromised.
    Impact
    Each malicious version injects a `preinstall` hook that executes a 498KB obfuscated Bun script, using the GitHub API as a covert exfiltration channel.
    Root cause
    Compromised publisher account or release of a legitimate package LLM03ASI04AML.T0010
    Sources
    OSV MAL-2026-4069: Malicious code in @antv/mcp-server-chart (npm)GitHub advisory GHSA-qgmj-c898-99rqsafedep.iosocket.devsafedep.io MCP Server Watch
    Evidence (2 quotes)
    What happened: “Malicious code in @antv/mcp-server-chart (npm)” source
    Impact: “Each malicious version injects a `preinstall` hook that executes a 498KB obfuscated Bun script, using the GitHub API as a covert exfiltration channel.” source
  21. AuditTeam OpsAgent framework used in ransomware-style extortion campaign across several countries

    AI safeguard bypass / misuse

    2026-01 (date stated by the source) · Organizations in Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China

    What happened
    The AuditTeam threat group used the OpsAgent framework, described as a penetration testing-like utility, to compromise organizations and demand an "Audit & Consulting fee" in ransom notes.
    Impact
    Dozens of organizations infected across several countries; stolen data archive threatened with public release unless a fee is paid.
    Root cause
    Malicious implant framework used for extortion; not an AI product vulnerability AML.T0053
    Sources
    The forced audit: how AuditTeam’s OpsAgent framework masks ransomware as consulting ThreatDeck story
    Evidence (4 quotes)
    What happened: “AuditTeam is an active threat group that uses the OpsAgent framework to compromise organizations across at least seven countries and territories.” source
    Victim: “the group has infected dozens of organizations in Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China” source
    Impact: “the group has infected dozens of organizations in Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China” source
    Date: “The campaign began in January 2026 and remained active through October 2026, at a minimum.” source
  22. Malicious code in @browserbasehq/mcp-server-browserbase (npm)

    AI-tool supply chain

    2025-11-25 (first reported) · @browserbasehq/mcp-server-browserbase

    What happened
    OSV lists version 2.4.2 of the npm package @browserbasehq/mcp-server-browserbase, shipped by an MCP server tracked by MCP Server Watch, as malicious; the record describes the package as compromised.
    Impact
    The malicious payload steals tokens and credentials and publishes them to GitHub.
    Root cause
    Compromised publisher account or release of a legitimate package LLM03ASI04AML.T0010
    Sources
    OSV MAL-2025-191196: Malicious code in @browserbasehq/mcp-server-browserbase (npm)www.aikido.devwww.wiz.iowww.stepsecurity.io MCP Server Watch
    Evidence (2 quotes)
    What happened: “Malicious code in @browserbasehq/mcp-server-browserbase (npm)” source
    Impact: “The malicious payload steals tokens and credentials and publishes them to GitHub.” source
  23. Malicious code in @postman/postman-mcp-server (npm)

    AI-tool supply chain

    2025-11-24 (first reported) · @postman/postman-mcp-server

    What happened
    OSV lists versions 2.4.11, 2.4.10, 2.4.12 of the npm package @postman/postman-mcp-server, shipped by an MCP server tracked by MCP Server Watch, as malicious; the record describes the package as compromised.
    Impact
    The malicious payload steals tokens and credentials and publishes them to GitHub.
    Root cause
    Compromised publisher account or release of a legitimate package LLM03ASI04AML.T0010
    Sources
    OSV MAL-2025-190909: Malicious code in @postman/postman-mcp-server (npm)www.aikido.devwww.wiz.iowww.stepsecurity.io MCP Server Watch
    Evidence (2 quotes)
    What happened: “Malicious code in @postman/postman-mcp-server (npm)” source
    Impact: “The malicious payload steals tokens and credentials and publishes them to GitHub.” source

Methodology

Built from stored source text only: every fact on an entry is backed by a verbatim quote from a cited source, checked word for word. Root-cause classes and OWASP/ATLAS ids are ThreatDeck's classification. Entries restate what the sources report; they are not findings of fault.

  • Candidates: ThreatDeck stories about attacks on AI systems (exploitation, breaches, malware, campaigns) and breaches that name an AI product, plus OSV malicious-package records for packages shipped by MCP servers that MCP Server Watch tracks.
  • A language model reads the stored article text and proposes the date, victim, what happened, impact and root cause. An entry is kept only if the victim is named in the stored text and the event quote matches it word for word; impact and dates are kept only with their own matching quote or an explicitly written date. Everything else is dropped.
  • Disclosures without a reported real-world event, research demos, warnings and predictions are left out. Wording is neutral; entries describe events, not blame.
  • "First reported" dates are the earliest publication among the cited sources. Root-cause classes and OWASP/ATLAS ids are ThreatDeck's classification.
  • Malicious-package entries restate the OSV record; the package may have been removed from its registry since.

Corrections

Corrections: if an entry is wrong, incomplete or unfair to a named organisation, write to the contact address on /security/ with the entry id and a source. Corrected entries are updated in place; removed entries disappear from the page, the feed and the JSON on the next publish. Contact: hello@threatdeck.net.

Following

Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

Presets

Get updates

A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.