OSINT Threat Intelligence Feeds, Curated by Analysts

OSINT threat intelligence feeds are easy to find and hard to use: thousands of domains, IP addresses and hashes a day, most of them irrelevant to you and some of them wrong. We select the open sources that fit your environment, filter and verify what they publish, and deliver a short, scored stream your SOC can load and trust.

  • Sources chosen for your stack
  • Analyst-verified indicators
  • Scores and expiry dates
  • STIX, CSV or plain-language delivery
Short answer

OSINT threat intelligence feeds are streams of indicators, such as malicious URLs, domains, IP addresses and file hashes, published by open projects, researchers and public agencies. Curated by analysts, they are filtered for your technology stack and sector, checked for false positives, scored, given an expiry date and delivered in a format your tools accept. OSINT-S does not sell a public feed; the curated output is built for and delivered to you.

Free OSINT Feeds vs Analyst-Curated Intelligence

Free feeds are a good raw material; curation decides which indicators reach your blocking tools and which go to your analysts.

Free or open feedsCurated for one organization
CoverageBroad, global, the same for every subscriberSelected for your sector, regions and technology
VolumeHigh, often updated every few minutesLower, limited to what concerns you
Quality checksVary by project; usually automatedAnalyst review of high-impact indicators before delivery
ContextIndicator, type, date, sometimes a malware familyWhy it matters to you, related actor or campaign, recommended action
LifespanIndicators often stay listed long after they stop being maliciousEach indicator carries an expiry date

Good open projects are generous. abuse.ch's URLhaus, for example, publishes malware distribution URLs as CSV and JSON dumps, DNS blocking zones and IDS rules, regenerated every five minutes and free under fair-use terms, while companies may need a paid subscription for its commercial API (URLhaus API). The terms of each source decide how we can use it on your behalf, so licensing is checked before a source goes into your feed.

Where Feed Noise and False Positives Come From

Most bad indicators are not fabricated; they are shared, stale or out of context. Blocking them causes outages, and alerting on them wastes analyst time.

  • Shared infrastructure. One IP address on a content delivery network or cloud host can serve thousands of legitimate sites alongside one malicious page.
  • Stale indicators. Phishing domains are abandoned within days and IP addresses are reassigned, but entries linger in feeds.
  • Compromised legitimate sites. A hacked small-business website that hosted malware last month may be clean now; blocking the whole domain breaks real traffic.
  • Popular services. File-sharing, URL-shortener and code-hosting domains appear in malicious URLs constantly and cannot be blocked wholesale.
  • Duplication. The same indicator arriving from five feeds looks like five confirmations when it is one report copied.

Feed builders know this: URLhaus, for instance, leaves the most popular domains out of its hostfile. Curation takes the same idea further, using your own asset list and traffic patterns.

How We Curate Feeds for Your Stack

Start from your environment, choose sources to match, filter and verify, then score, expire and deliver, with your SOC's feedback closing the loop.

  1. Map your environmentTechnology stack, internet-facing services, cloud providers, sector and regions, plus the tools that will consume the feed.
  2. Select sourcesOpen projects, public agency advisories, vulnerability disclosures, researcher publications and criminal-channel monitoring that fit that profile.
  3. Filter for relevanceDrop indicators for platforms you do not run and campaigns that do not reach your sector; keep what touches your stack or suppliers.
  4. Verify and enrichAnalysts check high-impact indicators against shared hosting, popular services and current status, and add actor, campaign and context.
  5. Score and expireEach indicator gets a confidence score, a recommended action (block, alert or watch) and an expiry date.
  6. Deliver and tuneIndicators and summaries arrive in agreed formats; your team's false-positive reports feed back into the filters.

Delivery Formats: STIX, TAXII, CSV and Plain Language

Machine-readable formats for your tools, written summaries for people. Formats are agreed during scoping so nothing needs reformatting at your end.

FormatWhat it isBest for
STIX 2.1A language and serialization format for exchanging cyber threat intelligence, maintained at OASISIndicators with relationships to actors, campaigns and malware
TAXII 2.1An application-layer protocol over HTTPS designed to carry STIX contentThreat intelligence platforms and SIEMs that poll collections
CSV or JSON listsFlat indicator lists with type, score and expiryFirewalls, proxies, DNS filters and simple scripts
Written alerts and digestsShort notes on what changed, why it matters and what to doSecurity leadership and smaller IT teams

Descriptions of STIX and TAXII follow the OASIS cyber threat intelligence documentation (OASIS CTI). Teams that want indicators pushed into their own pipelines or AI tooling can combine curation with OSINT automation and API work.

A Curated OSINT Service, Not a Feed Subscription

We do not sell a public feed product. What you receive is analyst output for your organization, built from sources whose terms allow it.

Your feed is one strand of our OSINT services for security teams. It is fed by the same analyst-reviewed monitoring platform, which updates hourly, that drives leaked credential monitoring, so a stealer log or a look-alike domain aimed at you can appear in the same stream as malware infrastructure. Indicators from an OSINT threat actor profile or from phishing intelligence are added as those cases run.

Setup, from environment mapping to first delivery, is quoted at a fixed price after written scoping and usually takes from 10 business days. Before you pass curated indicators on to an ISAC or peers, check your sharing rules: in the SANS 2026 CTI Survey, 55% of organizations lacked legally reviewed CTI sharing processes (SANS 2026).

Turn Feeds Into Something Your SOC Uses

Tell us your stack, your tools and which feeds you already pull. We will show what curation would keep, drop and add.

OSINT Threat Intelligence Feeds FAQ

We already pull a dozen free OSINT threat intelligence feeds into our SIEM, but my analysts say most alerts are junk — what would curated feeds change for a team of three?

Fewer, better alerts. Curated OSINT threat intelligence feeds start from your environment, not from the feed: indicators for platforms you do not run are dropped, high-impact ones are checked against shared hosting and popular services, and each one carries a score, a recommended action and an expiry date. Your analysts' false-positive reports then tune the filters. Most teams keep their free feeds as raw input; curation decides what reaches blocking tools.

Our firewall blocked a cloud provider's IP last month because it was on an open feed, and half our staff lost access to a supplier portal — how do you stop that happening?

By checking shared infrastructure before an indicator is marked for blocking. Cloud and content delivery IP addresses can serve thousands of legitimate sites, so analysts look at what else lives on an address before recommending a block, and many such indicators are delivered as alert-only. Expiry dates stop stale entries lingering. If you send us your critical suppliers and services, they go on an allowlist that indicators are checked against.

Can you deliver indicators as STIX over TAXII so our threat intelligence platform can poll them, or do we have to import spreadsheets by hand?

Machine-readable delivery is agreed at scoping, and STIX 2.1 objects are one of the options alongside CSV and JSON lists. STIX is a language and serialization format for exchanging cyber threat intelligence, and TAXII is the protocol over HTTPS designed to carry it (OASIS CTI). We confirm what your platform accepts during setup, so indicators arrive in a form it can ingest without manual reformatting.

Is it legal and allowed by the licenses to take indicators from free community feeds and have you pass them to us as part of a paid service?

It depends on each source's terms, which is why licensing is checked before a source goes into your feed. Some projects are free for everyone; others are free under fair-use terms but expect companies to take a commercial subscription, as abuse.ch does for its enhanced URLhaus API (URLhaus). Where a source requires your own subscription, we tell you and work from your access.

We run a fairly standard Microsoft and AWS environment in one country — how is a feed curated for us different from one curated for a bank or a hospital?

The sources overlap; the filters do not. For your environment, indicators tied to identity attacks on Microsoft 365, AWS credential abuse and exploited vulnerabilities in the products you expose are kept and ranked higher, while campaigns aimed at platforms you do not use are dropped. A bank's feed would weight payment fraud and banking malware; a hospital's would weight medical device and healthcare ransomware activity.

Do you sell a threat intelligence feed we could subscribe to like the big vendors, and how long does it take to set up curated feeds for us?

No, we do not sell a public feed product. What you receive is analyst output built for your organization from open and commercially available sources, drawn from an analyst-reviewed monitoring platform that updates hourly. Setup, from mapping your environment to the first delivery, is quoted at a fixed price after written scoping and usually takes from 10 business days, after which indicators and summaries arrive on the agreed schedule.

Sources and Notes

Sources checked 8 October 2026. Figures about third-party firms and tools are as published by them or by the cited source on that date.

Related pages