An extendable tool to extract and aggregate IOCs from threat feeds. Integrates out-of-the-box with ThreatKB and MISP, and can fit seamlessly into any existing worflow with SQS, Beanstalk, and custom plugins.
ThreatIngestor can be configured to watch Twitter, RSS feeds, or other sources, extract meaningful information such as malicious IPs/domains and YARA signatures, and send that information to another system for analysis.
ThreatIngestor requires Python 3.6+, with development headers.
Install ThreatIngestor from PyPI:
pip install threatingestor
Install optional dependencies for using some plugins, as needed:
pip install threatingestor[all]
View the full installation instructions for more information.
Create a new
config.yml file, and configure each source and operator module you want to use. (See
config.example.yml for layout.) Then run the script:
By default, it will run forever, polling each configured source every 15 minutes.
View the full ThreatIngestor documentation for more information.
ThreatIngestor uses a plugin architecture with “source” (input) and “operator” (output) plugins. The currently supported integrations are:
- Beanstalk work queues
- Git repositories
- GitHub repository search
- RSS feeds
- Amazon SQS queues
- Generic web pages
View the full ThreatIngestor documentation for more information on included plugins, and how to create your own.
Threat Intel Sources
Looking for some threat intel sources to get started? InQuest has a Twitter List with several accounts that post C2 domains and IPs: https://twitter.com/InQuest/lists/c2-feed. Note that you will need to apply for a Twitter developer account to use the ThreatIngestor Twitter Source. Take a look at
config.example.yml to see how to set this list up as a source.
For quicker setup, RSS feeds can be a great source of intelligence. Check out this example RSS config file for a few pre-configured security blogs.