Each item carries a free detection in Sigma, Splunk SPL and KQL where one exists, plus sample IOCs.
New threats from Threadlinqs Intelligence, written for a reader and a SIEM: the summary, the severity, the MITRE ATT&CK techniques, a detection you can paste into your stack, and the sources behind it.
The feed URL is https://intel.threadlinqs.com/feed.xml. Paste it into any reader.
Most threat intelligence feeds stop at a headline and a link. Each item in this feed is a small, complete briefing: the analysis, then the detection that goes with it, in the three languages a detection engineer actually deploys.
A readable summary in real paragraphs, cut at a sentence boundary with a link to the full analysis, and the severity: Critical, High, Medium or Low.
The ATT&CK techniques observed in the threat, listed by ID so you can map the item to your coverage.
The threat's free detection: its title, then the rule in Sigma, Splunk SPL and Microsoft KQL, each in its own code block. A body that fails our shape check is left out, not shown broken.
The remaining detections for the threat are listed by title, marked unlock with TL Creds. Their rule bodies are not in the feed.
Three indicators per threat, defanged and marked TLP:CLEAR, with a count of how many the threat has in total. The full indicator set unlocks with TL Creds.
Up to five outbound links to the original reporting the item is built from, so you can check it yourself.
One canonical address for the main feed. It lists the newest 50 threats; add ?limit= for more or fewer (the value snaps to 20, 50 or 100).
RSS 2.0 at /feed.xml, JSON Feed 1.1 at /feed.json. Both carry the same items. The older spellings /rss.xml, /atom.xml, /feed and /rss redirect to /feed.xml.
| Severity | RSS | JSON Feed |
|---|---|---|
| Critical | /feed/severity/critical.xml | .json |
| High | /feed/severity/high.xml | .json |
| Medium | /feed/severity/medium.xml | .json |
| Low | /feed/severity/low.xml | .json |
| Category | RSS | JSON Feed |
|---|---|---|
| Vulnerability | /feed/category/vulnerability.xml | .json |
| Malware | /feed/category/malware.xml | .json |
| Supply Chain | /feed/category/supply-chain.xml | .json |
| Phishing | /feed/category/phishing.xml | .json |
| Ransomware | /feed/category/ransomware.xml | .json |
| APT | /feed/category/apt.xml | .json |
| Threat Intelligence | /feed/category/threat-intel.xml | .json |
| Data Breach | /feed/category/data-breach.xml | .json |
| Zero-Day | /feed/category/zero-day.xml | .json |
| ICS/SCADA | /feed/category/ics-scada.xml | .json |
| Cloud Security | /feed/category/cloud.xml | .json |
Feeds are served from a short edge cache, so a new threat can take up to about 15 minutes to appear in the main feed and up to 30 minutes in the severity and category feeds.
https://intel.threadlinqs.com/feed.xml.https://intel.threadlinqs.com/feed.xml as the URL and choose the report types the items should create.Any other reader or SIEM that accepts RSS 2.0 or JSON Feed works the same way: add the URL, set a polling interval of 15 minutes or more, and filter on the severity or category feeds if you only want part of the stream.
© 2026 Threadlinqs. Indicator samples are TLP:CLEAR.
Browse the full corpus of threats, CVEs and actors at intel.threadlinqs.com, read the daily debrief, or connect an assistant through the MCP server.