
Current version: v1.0 Muninn
A Python tool for automating intelligence gathering, testing and reporting. O.D.I.N. is still in active development and is incomplete. Feedback on issues is welcome!
Note: O.D.I.N. is designed to be run on Linux. About 90% of it will absolutely work on Windows or MacOS with Python 3 and a copy of urlcrazy, but
extract, used for pulling metadata from non-PDF files, is exclusive to Linux. You'll be fine using an OS without access toextract, but you'll see some warnings and get less information.
O.D.I.N. is made possible through the help, input, and work provided by others. Therefore, this project is entirely open source and available to all to use/modify. All this developer did was assemble the tools, convert some of them to Python 3, and stitch them together.
O.D.I.N. is still very much in development, but it aims to automate many of the common recon tasks carried out by penetration testers. Such as: * Harvesting email addresses and employee names for a company. * Linking employees and companies to social media profiles. * Checking to see if discovered accounts have been a part of any public security breaches or appeared in any pastes. * Collecting data on domains and IP addresses from Shodan, Censys, DNS records, and whois/RDAP. * Discovering subdomains, their related IP addresses, and looking for CDNs that might allow for domain fronting. * Hunting Office files and PDFs under a domain, downloading them, and extracting metadata. * Linking key words, like a company name or domain, to AWS via S3 buckets and account aliases. * More to come in the future...
cd into the /setup directory and run setup_check.py to make sure your keys.config file is in order.pip3 install -r requirements.txt or python3 -m pip install -r requirements.txtIf you'd like to have O.D.I.N. do recon against AWS you will need an IAM user account and the associated ID and Secret. Get this from your AWS console. Typically, you will place this in ~/.aws/credentials, but it's nice to keep everything in one place. O.D.I.N. will use your keys.config file, but Amazon's Boto3 library for AWS may still look at ~/.aws/credentials. If that file has errors, Boto3 may log an error and quit. Just be aware of this possibility in case you have/use ~/.aws/credentials.
O.D.I.N. uses several APIs to gather information. Some of these require an API key, but they're mostly free. That is to say, you can get a free key or pay for more requests/day. Shodan is a good example of this.
Both of these services are used to collect data on domains and IP addresses. This includes attaching domains to IP addresses, identifying the network CIDRs for these addresses, and pulling information about the owners.
No API key is needed.
Shodan is used to search for domains and lookup hosts (IP addresses). This pulls in information like open ports, banners, hostnames, and location data. Shodan also flags hosts for well known vulnerabilities like Heartbleed. This data is recorded as well, if it exists.
Sign-up for an account to get your API key: shodan.io
Censys is very much like Shodan, except less information about open ports/services is available. However, Censys provides a way to search for certificates tied to a domain. This can be a lot of data, but you may find new hosts, like those tied to an employee's email address and used for a VPS in the cloud.
Sign-up for an account to get your API key: censys.io
URLVoid offers reputation data for domains, including Alexa and Google rankings, domain age, and location data. It also keeps track of domains that have been flagged for malicious activity by various entities (e.g. Fortinet, Avira).
This may be the most "skippable" of the APIs, but some of the data can be useful and worthwhile. It's included for those occasions.
Sign-up for an account to get your API key: urlvoid.com/api
If you setup a Twitter app for O.D.I.N., the tokens can be used with Tweepy and TheHarvester to not only locate Twitter handles tied to the provided domain but also collect account data (e.g. real name, location, follower count, and user description).
In the future, this may be used to also collect analytics from Twitter to help you find very active users or get a profile of them.
Become a Twitter developer by going to dev.twitter.com and then create an app on apps.twitter.com.
eSentire's Cymon is used to check domains and IP addresses to see if the target appears in any of Cymon's collected threat intelligence feeds. This is used for reputation checks, but also used in combination with urlcrazy to check similar, registered domains to see if the domain or the domain's A-record IP addresses have been reported.
Note that appearing in a threat feed doesn't mean something is wrong or that Cymon has bad data. A domain may have been used for phishing, been detected and seized, and is now dormant with the old malicious A records. Then you have things like cloud service IPs that change hands often. Events like that can lead to a domain or IP being flagged a week ago and no longer being malicious. Always investigate these findings.
Sign-up for an account to get your API key: cymon.io
Email addresses are checked against HIBP to determine if any email addresses for the organization have been mentioned in any pastes or been involved in any security breaches.
No API key is needed.
DNS Dumpster is a cool project you can find at dnsdumpster.com. Subdomain information is collected from DNS Dumpster, including a neat domain map image!
No API key is needed.
Meant for marketing folks to find leads and contacts at a company, this service offers free API keys for harvesting their contact information organizaed by company/domain. Hunter will return names, email addresses, phone numbers, Twitter handles, LinkedIn profile links, and job titles.
Sign-up for an account to get your API key: hunter.io
Full Contact support is implemented only for their Company API at the moment, but support for the People API may come in the future. For now, this is used to build a company profile based on a target domain, such as the client's primary domain used for email and their website. Full Contact catalogues everything from website info and company logo(s) to website blurbs and social media profiles.
It's likely Full Contact will get some things wrong, such as number of employees. It's usually not really wrong, but the profile is meant to act as a snapshot to get you started.
Sign-up for an account to get your API key: app.fullcontact.com
Yes, Amazon Web Services. With an AWS IAM user's Access ID and Secret, the AWS API can be leveraged to do recon against AWS to find things like S3 buckets and accounts names and aliases. Account names are strings of numbers, so you will need some idea of what you're looking for there. Aliases, however, can be anything, like a company name, and those can be validated as existing or not.
By default, O.D.I.N. uses the client (-c) name and domain (-d) for searches. O.D.I.N. will search for the name with spaces stripped out, the domain with the TLD, and the domain without the TLD. An optional wordlist can be provided with --aws. Keywords can be anything, really. Consider assembling a list of related words or running a tool like cEWL to generate one.
Setup an IAM user on any Amazon account to get an Access ID and Secret.
I get this syntax error. What's the deal?
Please make sure you are using Python 3, not Python 2.7 or earlier. I don't write tools in Python 2.x and O.D.I.N. will not work when run with Python 2.x.
I get an error when O.D.I.N. tries to import a library. What's wrong?
Like above, please make sure you are using Python 3. O.D.I.N. must be run in Python 3 and the requirements must be installed using pip for Python 3. To ensure Python 3 is used, just in case the pip commands are tied to another version, run this command: python3 -m pip install -r requirements.txt
Why not Clearbit?
Clearbit looks useful for OSINT, but the free tier is restricted to 20 API calls in a month. That may even be 20 API calls for the life of the accounts. The details are unclear. Either way, that's very restrictive and I want O.D.I.N. to be as simple and free to use as possible.
Why not use FullContact's People API?
Currently only the Company API is used. There are plans to incorproate the People API in the future.
Does O.D.I.N. perform DNS brute forcing?
No. This is being considered, but brute forcing can take a long time and there are many tools that take care of this quite well. Those tools are not so easy to incorporate into O.D.I.N. without just running the commands for those tools. Look to Fierce and DNSRecon for this.
That does not mean more subdomain goodies are not coming. Some opportunities are being investigated and optional DNS brute forcing is probably happening in the future.
I don't have X API key, can I still use O.D.I.N.?
Absolutely. If an API key is missing from the keys.config file, any checks using those keys will be skipped. You are strongly encouraged to go get the free API keys to get the most out of the tools, but you can skip any you don't want.
A big thank you to a few contributors who gave me the OK to re-use some of their code:
And to these folks who have created/maintained some of the tools integrated into O.D.I.N.: