Written and maintained by CASRAI Editorial Board
Published · Last updated
On this page
ThreatFox is a free, community-driven platform run by abuse.ch for sharing indicators of compromise (IOCs): IP addresses, domain names, URLs, email addresses and file hashes that, if seen in a production environment, would indicate a malware compromise. You can browse it in a web interface, query it through a JSON API at threatfox-api.abuse.ch, or download exports for security tools. Both the API and the exports need a free Auth-Key, and since 2025-05-01 IOCs older than six months are no longer served by the API or the exports.
This guide covers the API query types, the export formats and their refresh intervals, how to read a ThreatFox record, and how ThreatFox relates to its sister platforms URLhaus and MalwareBazaar. Documentation was read on 2026-11-12 at the official ThreatFox pages listed under Sources.
What ThreatFox is used for in research
The ThreatFox FAQ explains the problem it addresses: analysts and researchers publish IOCs on GitHub or social media, which makes them costly to find and hard to automate against. ThreatFox gives contributors one place to share indicators and gives consumers one API to collect them. The platform offers a web interface and an API for both directions.
For research and teaching in threat intelligence, three properties matter:
- Malware-only scope. The submission policy limits ThreatFox to IOCs related to malware. Spam, phishing and other threats are explicitly excluded, so the dataset is narrower than a general abuse feed.
- Malware family labels. Each IOC is tied to a malware family using the labels from Malpedia, and the API returns a Malpedia link and any aliases with each record, which makes family-level grouping possible without your own label mapping.
- Machine access. Every record can be fetched by API or export, so a study can be scripted and its collection date documented. Exports can also be loaded into tools such as MISP (daily MISP events).
The platform’s own FAQ reports that, as of October 2024, ThreatFox answered around 95 million API requests in 30 days and had received over 1.97 million shared IOCs. Treat these as the operator’s statistics from that date, not current figures.
Which abuse.ch platform for which indicator
abuse.ch runs several related projects. At the time ThreatFox launched on 8 March 2021, the announcement positioned it against two existing platforms: URLhaus tracks malware distribution sites, MalwareBazaar collects malware samples, and ThreatFox covers the wider set of IOCs, such as botnet command-and-control infrastructure, that do not fit either.
| You have or want | Start with | Why (per abuse.ch) |
|---|---|---|
| A URL suspected of distributing malware | URLhaus | Tracks malware distribution sites |
| A malware file or its hash | MalwareBazaar | Collects and shares malware samples |
| An IP:port, domain or URL tied to a botnet C2 server, or indicators for a named malware family | ThreatFox | Shares IOCs of several types, each linked to a malware family |
| The samples behind a ThreatFox IOC | ThreatFox by-ID lookup, then MalwareBazaar | The by-ID response lists related samples with MD5, SHA256 and a MalwareBazaar link |
How to install or access it
There is nothing to install. ThreatFox is a hosted service.
- Web interface:
https://threatfox.abuse.ch/. The menu offers Browse IOCs, Share IOCs, IOC Requests, the API and Export pages, Statistics and the FAQ. - Auth-Key: create a free key at the abuse.ch Authentication Portal,
https://auth.abuse.ch/. The API documentation marks the Auth-Key as required, and every API request must send it in anAuth-KeyHTTP header. Export downloads need the key in the URL. - API endpoint:
https://threatfox-api.abuse.ch/api/v1/, called with HTTP POST and a JSON body. - Terms: the community API is free under abuse.ch fair use principles. Use by companies, networks or individuals with commercial or for-profit needs may require a paid subscription to the enhanced abuse.ch commercial API. Read the Terms of Use linked from the ThreatFox footer before building a service on the data.
Step-by-step: query the ThreatFox API
The steps below use the curl pattern from the official API page. Replace YOUR-AUTH-KEY with your key.
Step 1: Pull recent IOCs
The get_iocs query returns IOCs filtered by first-seen time. The days parameter accepts 1 to 7 and defaults to 3.
curl -H "Auth-Key: YOUR-AUTH-KEY" -X POST https://threatfox-api.abuse.ch/api/v1/ -d '{ "query": "get_iocs", "days": 1 }'
Step 2: Search for a specific indicator
Use search_ioc with a search_term. By default the search is a wildcard search; set exact_match to true to search for the exact IOC.
curl -H "Auth-Key: YOUR-AUTH-KEY" -X POST https://threatfox-api.abuse.ch/api/v1/ -d '{ "query": "search_ioc", "search_term": "139.180.203.104", "exact_match": true }'
Step 3: Look up IOCs for a malware family or tag
The malwareinfo query takes a malware name and an optional limit; taginfo takes a tag and an optional limit. The default limit is 100 and the maximum is 1,000.
curl -H "Auth-Key: YOUR-AUTH-KEY" -X POST https://threatfox-api.abuse.ch/api/v1/ -d '{ "query": "malwareinfo", "malware": "Cobalt Strike", "limit": 10 }'
Step 4: Find the IOCs tied to a file hash
Use search_hash with an MD5 or SHA256 value in the hash field.
curl -H "Auth-Key: YOUR-AUTH-KEY" -X POST https://threatfox-api.abuse.ch/api/v1/ -d '{ "query": "search_hash", "hash": "2151c4b970eff0071948dbbc19066aa4" }'
Step 5: Fetch one record by ID
curl -H "Auth-Key: YOUR-AUTH-KEY" -X POST https://threatfox-api.abuse.ch/api/v1/ -d '{ "query": "ioc", "id": 41 }'
The by-ID response is the fullest: in the documentation’s example it adds a comment, credits and a malware_samples list with MD5, SHA256 and MalwareBazaar links.
API query types at a glance
query value |
Parameters | Returns |
|---|---|---|
get_iocs |
days (optional, 1 to 7, default 3) |
Recent IOCs by first-seen time |
ioc |
id |
One IOC with comment, credits and linked samples |
search_ioc |
search_term; optional exact_match (default false, wildcard) |
Matching IOCs |
search_hash |
hash (MD5 or SHA256) |
IOCs associated with the file hash |
taginfo |
tag; optional limit (default 100, max 1,000) |
IOCs carrying the tag |
malwareinfo |
malware; optional limit |
IOCs for the malware family |
get_label |
malware; optional platform (win, osx, apk, jar or elf) |
Malpedia-based malware labels matching the name |
malware_list |
none | Malware families known to ThreatFox |
types |
none | Supported threat type and IOC type combinations |
tag_list |
none | Tags known to ThreatFox, with first and last seen |
submit_ioc |
see Sharing IOCs below | Submits IOCs |
Output and how to read it
Query responses are JSON with a query_status field (the examples show ok) and a data field. Each IOC record carries these fields:
| Field | Meaning |
|---|---|
id |
ThreatFox IOC ID, usable with the ioc query |
ioc |
The indicator itself, for example a domain, a URL or an ip:port combination |
threat_type, ioc_type |
What the indicator identifies (for example botnet_cc, a botnet command-and-control server) and what kind of value it is; the _desc fields explain each |
malware, malware_printable, malware_alias, malware_malpedia |
Malpedia family label (for example win.cobalt_strike), display name, aliases and the Malpedia page |
confidence_level |
Number from 0 to 100 set by the reporter; the default on submission is 50 |
first_seen, last_seen |
UTC timestamps; last_seen can be null |
reference, reporter, tags |
Source link, who reported it, and free-form tags |
Read confidence_level with care. The FAQ tells submitters to choose it carefully and to use a high value only for manually vetted IOCs, but it does not define the scale beyond 0 to 100, so a value is the reporter’s judgement, not a calibrated probability.
Expiry: what the six-month rule changes
Since 2025-05-01, ThreatFox expires IOCs older than six months. abuse.ch gives the reason as avoiding false positives, mostly on cloud infrastructure where assets such as IP addresses change customers quickly. The effect differs by access route:
- API and exports: expired IOCs are not exposed.
- Web interface: expired IOCs remain visible and searchable, flagged as expired.
- MISP feed: the export page recommends removing the IOC flag on events older than six months to avoid false positives.
- Recent-IOC API query: separately,
get_iocsdoes not return IOCs older than 7 days, for performance reasons. For a larger set, use a data export.
For a historical study this means the API alone cannot reconstruct older activity. Record the date you pulled any export, because the same query run later can return a different set.
Export formats and refresh intervals
The data table below lists the export formats ThreatFox documents, with the refresh interval and time window each states. All exports need an Auth-Key. A full CSV export is requested like this:
curl -i "https://threatfox-api.abuse.ch/v2/files/exports/YOUR-AUTH-KEY-HERE/full.csv.zip"
For the host file, Suricata ruleset and RPZ, abuse.ch recommends fetching every 5 minutes for the best protection, matching the generation interval. Do not poll faster than the file is regenerated.
Sharing IOCs
Anyone with an Auth-Key can share IOCs through the Share IOCs page or the submit_ioc query. Required fields are threat_type, ioc_type, malware (a Malpedia name, found with get_label or malware_list) and iocs. Optional fields include confidence_level, is_compromised, reference, tags, comment and anonymous. The submission policy asks for confirmed, vetted IOCs only, and the FAQ says submissions are reviewed by a human unless the account has been flagged as a Trusted Reporter. Do not submit IOCs older than 10 days. Repeated policy violations can lead to a ban from contributing.
Troubleshooting
- Requests are refused or return no data. Confirm the
Auth-Keyheader is present on API calls and that the key is embedded in the export URL. The key is required for both. - An older indicator is missing from the API. It may have expired under the six-month rule, or it is older than the 7-day window of
get_iocs. Search for it in the web interface, which still shows expired IOCs, or usesearch_ioc. - A search returns more than you expected.
search_iocdoes wildcard matching unlessexact_matchistrue. - A submission is rejected or not visible yet. Check that the malware name is a valid Malpedia label and that the threat type and IOC type combination appears in the
typesresponse. New submissions are vetted by a human unless you are a Trusted Reporter. - You need STIX/TAXII. The FAQ lists this as a question (why there is no STIX/TAXII export); the documented formats are MISP, Suricata, RPZ, host file, JSON and CSV.
Free alternatives and companions
The abuse.ch platforms are the closest companions. Each guide below describes that platform’s own access rules.
| Platform | What it holds (per abuse.ch) | Guide |
|---|---|---|
| URLhaus | Malware distribution sites | URLhaus guide |
| MalwareBazaar | Malware samples | MalwareBazaar guide |
| ThreatFox | IOCs of several types linked to malware families | This page |
Related background: the exchange formats and platforms that consume IOC feeds, such as MISP and OpenCTI, are covered in the MISP and OpenCTI guides. ThreatFox data is also shared as open threat data, in the spirit of open data, but its use is governed by the abuse.ch Terms of Use.
FAQ
What is ThreatFox?
ThreatFox is a free, community-driven abuse.ch platform for sharing indicators of compromise related to malware, with a web interface, an API and downloadable exports.
Is ThreatFox free?
The community API is available free of charge under abuse.ch fair use principles. Companies, networks or individuals with commercial or for-profit needs may require a paid subscription to the enhanced abuse.ch commercial API, according to the API documentation.
Do I need an account or key?
You need a free Auth-Key from the abuse.ch Authentication Portal to call the API or download exports.
What IOC types does ThreatFox hold?
IP addresses, domain names, URLs, email addresses and file hashes, restricted to malware-related indicators.
Do ThreatFox IOCs expire?
Yes. Since 2025-05-01 IOCs older than six months are expired and are not returned by the API or exports. They remain visible in the web interface, flagged as expired.
How is ThreatFox different from URLhaus and MalwareBazaar?
URLhaus focuses on malware distribution sites and MalwareBazaar on malware samples. ThreatFox shares a wider range of IOCs, each linked to a malware family.
Sources
- ThreatFox Community API documentation, threatfox.abuse.ch/api, read 2026-11-12.
- ThreatFox Export page, threatfox.abuse.ch/export, read 2026-11-12.
- ThreatFox FAQ, threatfox.abuse.ch/faq, read 2026-11-12.
- abuse.ch, Introducing ThreatFox (8 March 2021), read 2026-11-12.
Data: ThreatFox export formats: refresh interval and data window
Export formats documented on the ThreatFox Export page (abuse.ch), with the generation interval and time window each states. Compiled from the official export documentation; 'Not stated' marks values the page does not give.
Period covered: 2025/2026.
| Export format | Content scope | Refresh interval | Time window |
|---|---|---|---|
| Daily MISP events | IOCs as MISP events | Daily | Not stated; abuse.ch advises removing the IOC flag on IOCs older than 6 months |
| Host file (domains only) | Payload delivery domains and botnet C2 domains | Every 5 minutes | Past 6 months |
| Suricata IDS ruleset | All network-based IOCs | Every 5 minutes | Past 6 months |
| DNS Response Policy Zone (RPZ) | Payload delivery domains and botnet C2 domains | Every 5 minutes | Past 6 months |
| JSON file | IOC data export | Not stated | Expired IOCs (older than 6 months) not exposed |
| CSV files | IOC data export | Not stated | Expired IOCs (older than 6 months) not exposed |
Sources
- ThreatFox Export (accessed 2026-11-12)
- ThreatFox Community API (accessed 2026-11-12)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







