Parse indicators of compromise from text. You can test this project here: http://ioc-finder.hightower.space/.
Currently, this package can the following items in a given text:
- IP address (IPv4 and IPv6)
- Email addresses (both standard format (e.g.
test@example.com
) and an email with an IP address as the domain (e.g.test@[192.168.0.1]
)) - Domain names (support for Unicode domain names (e.g.
ȩxample.com
) is coming soon) - URLs
- File hashes (md5, sha1, sha256, and sha512)
- Registry Key paths (e.g.
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
) - Autonomous System Numbers (ASNs) (in multiple formats such as
asn1234
andas 1234
) - CVEs (e.g.
CVE-2014-1234
) - CIDR ranges (currently ipv4 ranges; ipv6 ranges coming soon)
- Google Adsense Publisher IDs
- Google Analytics Tracker IDs
- Bitcoin addresses (P2PKH, P2SH, and Bech32)
- XMPP addresses (basically, this captures email addresses whose domain names contain "jabber" or "xmpp")
- MAC addresses
- Others... if you have any requests, let me know (or you can contact me here to make private suggestions)!
Also provides some helpful features like:
- Option to parse domain name from a URL
- Option to parse domain name from an email address
- Option to parse IP address from a CIDR range
To install this package:
pip install ioc-finder
This package can be used in python or via a [command-line interface](#Command-Line Interface).
The primary function in this package is the ioc_finder.find_iocs()
function. A simple usage looks like:
from ioc_finder import find_iocs
text = "This is just an example.com https://example.org/test/bingo.php"
iocs = find_iocs(text)
print('Domains: {}'.format(iocs['domains']))
print('URLs: {}'.format(iocs['urls']))
You must pass some text into the find_iocs()
function as string (the iocs will be parsed from this text). You can also provide the options detailed below.
The find_iocs
takes the following keywords (all of them default to True
):
parse_domain_from_url
(default=True): Whether or not to parse domain names from URLs (e.g.example.com
fromhttps://example.com/test
)parse_domain_from_email_address
(default=True): Whether or not to parse domain names from email addresses (e.g.example.com
fromfoo@example.com
)parse_address_from_cidr
(default=True): Whether or not to parse IP addresses from CIDR ranges (e.g.0.0.0.1
from0.0.0.1/24
)
See test_ioc_finder.py for more examples.
The find_iocs()
returns a dictionary in the following structure:
{
"asns": [],
"bitcoin_addresses": [],
"complete_email_address": [],
"cves": [],
"domains": [],
"email_addresses": [],
"google_adsense_publisher_ids": [],
"google_analytics_tracker_ids": [],
"ipv4_cidrs": [],
"ipv4s": [],
"ipv6s": [],
"md5s": [],
"registry_key_paths": [],
"sha1s": [],
"sha256s": [],
"sha512s": [],
"urls": [],
"xmpp_addresses": [],
"mac_addresses": []
}
For example, running the example code shown at the start of the usage section above produces the following output:
{
"asns": [],
"bitcoin_addresses": [],
"complete_email_address": [],
"cves": [],
"domains": ["example.org", "example.com"],
"email_addresses": [],
"google_adsense_publisher_ids": [],
"google_analytics_tracker_ids": [],
"ipv4_cidrs": [],
"ipv4s": [],
"ipv6s": [],
"md5s": [],
"registry_key_paths": [],
"sha1s": [],
"sha256s": [],
"sha512s": [],
"urls": ["https://example.org/test/bingo.php"],
"xmpp_addresses": [],
"mac_addresses": []
}
There are two grammars for email addresses. There is a fairly complete grammar to find email addresses matching the spec (which is very broad). Any of these complete email addresses (e.g. foo"bar@gmail.com
) will be sent as output to in complete_email_addresses
key.
Email addresses in the simple form we are familiar with (e.g. bar@gmail.com
) will be sent as output in the email_addresses
key.
The ioc-finder package can be used from a command line like:
ioc-finder "This is just an example.com https://example.org/test/bingo.php"
This will return:
{
"asns": [],
"bitcoin_addresses": [],
"complete_email_addresses": [],
"cves": [],
"domains": [
"example.com",
"example.org"
],
"email_addresses": [],
"google_adsense_publisher_ids": [],
"google_analytics_tracker_ids": [],
"ipv4_cidrs": [],
"ipv4s": [],
"ipv6s": [],
"md5s": [],
"registry_key_paths": [],
"sha1s": [],
"sha256s": [],
"sha512s": [],
"urls": [
"https://example.org/test/bingo.php"
],
"xmpp_addresses": [],
"mac_addresses": []
}
Here are the usage instructions for the CLI:
Usage: ioc-finder [OPTIONS] TEXT
CLI interface for parsing indicators of compromise.
Options:
--no_url_domain_parsing Using this flag will not parse domain names
from URLs
--no_email_addr_domain_parsing Using this flag will not parse domain names
from email addresses
--no_cidr_address_parsing Using this flag will not parse IP addresses
from CIDR ranges
--no_xmpp_addr_domain_parsing Using this flag will not parse domain names
from XMPP addresses
--help Show this message and exit.
This project uses the ioc_fanger package to make sure that all indicators in the text are properly fanged.
This package was created with Cookiecutter and Floyd Hightower's python-project-template project template.
Previous iterations of this package were inspired by https://github.com/mosesschwartz/extract_iocs.
You may also be interested in https://github.com/ioc-fang/ioc_fanger, a project to fang and defang indicators of compromise. For example,
defanging:
example.com => example[.]com
https://example.com => hXXps://example[.]com
and fanging:
example[.]com => example.com
example(.)com => example.com
me AT example(.)com => me@example.com
There are a number of projects available to find Indicators of Compromise. Your mileage may vary with them. If there are things that another package can do that you would like to see in this package, let me know (or contact me). Here are a few other ones: