Repository navigation
OSINT Investigation Procedures Guide
This guide provides step-by-step procedures for conducting thorough OSINT investigations on scam and fraud cases.
Step-by-step scam/fraud investigation procedures (email, phone, domain, IP, username, cryptocurrency) built around the osint_investigator.sh toolkit referenced throughout, ending in evidence preservation and abuse/IC3 reporting workflows. Distinct from ../OSINT_CHEATSHEET.md (generic command reference) and ../OSINT_GUIDE.md (methodology/background) - this is specifically the scam-investigation playbook with a defined case workflow from intake to law enforcement referral.
Ten sections following a single investigation from pre-investigation checklist through six identifier-specific procedures (email/phone/domain/IP/username/crypto), then evidence preservation, report generation, abuse reporting, and an IC3 submission checklist.
Take a scam/fraud complaint from intake to a submitted abuse report or IC3 filing, with properly hashed and timestamped evidence at every step for chain-of-custody integrity.
- Investigating a specific scam/fraud case (phishing, romance scam, tech support scam, investment fraud) end-to-end
- Needing the exact abuse-reporting workflow (registrar/hosting/email provider) after identifying responsible parties
- Preparing an IC3 submission for a fraud case involving financial loss
- Pre-Investigation Checklist
- Email Investigation Procedure
- Phone Investigation Procedure
- Domain Investigation Procedure
- IP Address Investigation Procedure
- Username Investigation Procedure
- Cryptocurrency Investigation Procedure
- Evidence Preservation
- Report Generation
- Abuse Reporting Workflow
Before starting any investigation:
- Create a new case with unique Case ID
- Document the incident/complaint in case notes
- Verify you have legal authorization to investigate
- Check that required tools are installed (
./osint_investigator.sh --status) - Verify API keys are configured
- Ensure adequate storage for evidence
YYYY-NNN-TYPE
Examples:
- 2024-001-PHISHING
- 2024-002-ROMANCE_SCAM
- 2024-003-TECH_SUPPORT
- 2024-004-INVESTMENT_FRAUD
Identify accounts associated with an email address, discover breach exposure, and gather intelligence for abuse reporting.
holehe target@email.com --only-usedWhat to look for:
- Registered accounts on social media platforms
- Partial recovery emails/phone numbers
- Account creation indicators
Document: List of discovered accounts
h8mail -t target@email.com -o breach_results.csvWhat to look for:
- Previous breaches containing the email
- Associated passwords (for correlation, not misuse)
- Related email addresses
Document: Breach exposure summary
The toolkit automatically queries HIBP when the API key is set.
What to look for:
- Breach names and dates
- Data types exposed
- Pattern of compromise
# Hunter.io verification (via toolkit)
# Or manual: curl "https://api.hunter.io/v2/email-verifier?email=target@email.com&api_key=YOUR_KEY"What to look for:
- Deliverable status
- MX records
- SMTP check results
- Disposable email detection
If you have the original scam email:
- Extract full headers from email client
- Analyze routing path
- Identify originating IP
- Check SPF/DKIM/DMARC alignment
- Look for spoofing indicators
Tools: mxtoolbox.com, emailheaders.net
Extract the domain from the email address and proceed to Domain Investigation.
Identify carrier, validate number, and discover associated online presence.
phoneinfoga scan -n "+1234567890"What to look for:
- Country and carrier
- Line type (mobile, VoIP, landline)
- Valid number confirmation
The phonenumbers library provides detailed carrier information:
import phonenumbers
from phonenumbers import carrier, geocoder
pn = phonenumbers.parse("+1234567890")
print(carrier.name_for_number(pn, 'en'))
print(geocoder.description_for_number(pn, 'en'))VoIP numbers are commonly used by scammers. Check for:
- Google Voice
- TextNow
- Burner app numbers
- Twilio/other API numbers
Use multiple sources:
- PhoneInfoga built-in searches
- Truecaller (manual check)
- Caller ID databases
- Social media search with phone number
Record:
- Full number with country code
- Carrier name
- Line type
- VoIP indicator
- Any associated names/addresses
Map the complete infrastructure behind a scam domain, identify hosting providers, and gather abuse contacts.
whois scam-domain.comWhat to look for:
- Registrant information (often privacy-protected)
- Registrar name and abuse contact
- Registration date (recent = suspicious)
- Nameservers
- Expiration date
Document: Registrar abuse contact for reporting
# A Records (IP addresses)
dig +short scam-domain.com A
# MX Records (mail servers)
dig +short scam-domain.com MX
# TXT Records (SPF, verification)
dig +short scam-domain.com TXT
# NS Records (nameservers)
dig +short scam-domain.com NSDocument: All IP addresses for IP investigation
subfinder -d scam-domain.com -silent -o subdomains.txtWhat to look for:
- admin.* subdomains
- api.* subdomains
- mail.* subdomains
- Hidden panels or services
cat subdomains.txt | httpx -td -server -title -asnWhat to look for:
- Web server type
- CMS platform
- Hosting provider
- CDN usage (may mask origin)
# Wayback Machine URLs
echo scam-domain.com | waybackurls > historical_urls.txt
# Certificate Transparency
curl -s "https://crt.sh/?q=%25.scam-domain.com&output=json" | jqWhat to look for:
- Previous content/pages
- Earlier registration
- SSL certificate history
- Related domains on same certificate
theHarvester -d scam-domain.com -l 500 -b allWhat to look for:
- Email addresses associated with domain
- Employee names
- Related domains/hosts
Identify the hosting provider, abuse contacts, and reputation of IP addresses.
asn 1.2.3.4This provides:
- ASN number and name
- Network range
- Abuse contact email
- Country
- RPKI status
Document: Abuse email for reporting
# Read-only lookup. Replace the illustrative address with a permitted IP.
IP="8.8.8.8"
curl --fail --silent --show-error --location \
--proto '=https' --proto-redir '=https' \
"https://rdap.org/ip/$IP" | jq '{name,handle,startAddress,endAddress,entities}'Interpretation: RDAP reports registry allocation details and possibly contact entities. It does not establish the IP's physical location, the end user's identity, whether the host is reachable, or that any address belongs to a malicious actor. Review RDAP.org's bootstrap documentation and the ARIN RDAP guide; responses vary by registry.
If city/country or proxy/VPN classifications are necessary, obtain them separately from an approved, HTTPS-enabled geolocation/reputation provider under the applicable license. Record the source, query date, precision, uncertainty and disclosure of the investigated address to the provider. Never substitute registry country for confirmed geolocation.
Shodan (if API configured):
curl -s "https://api.shodan.io/shodan/host/1.2.3.4?key=YOUR_KEY" | jqAbuseIPDB:
curl -s "https://api.abuseipdb.com/api/v2/check?ipAddress=1.2.3.4&maxAgeInDays=90" \
-H "Key: YOUR_KEY" | jqWhat to look for:
- Previous abuse reports
- Confidence score
- Types of abuse
- Open ports/services
Active testing requires written authorization and an explicitly in-scope target. Do not scan a third-party address simply because it appeared in an OSINT result. Replace the illustrative placeholder before running.
nmap -F -T2 --open AUTHORIZED_TARGET_IPWhat to look for:
- Web servers (80, 443)
- Mail servers (25, 587)
- Remote access (22, 3389)
- Unusual services
dig -x 1.2.3.4 +short
host 1.2.3.4What to look for:
- Hostname reveals hosting provider
- Shared hosting indicators
- VPS/cloud provider names
Discover all accounts associated with a username across social media and other platforms.
maigret scammer_username --pdf --html -o ./username_results/What to look for:
- Active social media accounts
- Forum registrations
- Dating site profiles
- Professional profiles
- Gaming accounts
sherlock scammer_username --csvUse as secondary verification for Maigret results.
Visit discovered profiles to:
- Confirm the account is actually the target
- Screenshot active profiles
- Document profile information
- Note connections/followers
- Check post history
For each confirmed profile:
- Bio/Description: Contact info, links, claims
- Profile Photo: Reverse image search
- Post History: Timeline, patterns
- Connections: Friends, followers, groups
- Activity: Posting frequency, times
# Use Google Images, TinEye, Yandex
# Or: https://images.google.com
# Upload profile photos to find other usesTrace cryptocurrency transactions and identify connections to known scam wallets.
- Bitcoin: Starts with 1, 3, or bc1
- Ethereum: Starts with 0x (40 hex chars)
- Litecoin: Starts with L, M, or 3
Manual checks:
- https://chainabuse.com/address/ADDRESS
- https://www.chainabuse.com/address/ADDRESS
- https://cryptoscamdb.org/search
Bitcoin:
curl -s "https://blockchain.info/rawaddr/ADDRESS?limit=50" | jqCheck:
- Total received/sent
- Number of transactions
- First/last transaction dates
- Balance
Ethereum:
# Etherscan API v1 was fully deprecated 2025-08-15 - v2 requires a chainid parameter (1 = Ethereum mainnet)
curl -s "https://api.etherscan.io/v2/api?chainid=1&module=account&action=txlist&address=ADDRESS&apikey=YOUR_KEY" | jqFor significant addresses:
- Identify first funding source
- Track outgoing transactions
- Look for exchange deposits
- Note clustering with other addresses
Record:
- Full address
- Blockchain type
- Total value transacted
- Abuse database results
- Transaction screenshots
- Hash Everything: SHA256 hash immediately upon collection
- Timestamp Everything: UTC timestamps for all evidence
- Document Chain of Custody: Log who collected what and when
- Multiple Copies: Original + working copy
- Integrity Verification: Regular hash checks
# 1. Monolith (self-contained HTML)
monolith https://scam-site.com -o evidence_$(date +%Y%m%d_%H%M%S).html
# 2. Screenshot
cutycapt --url=https://scam-site.com --out=screenshot_$(date +%Y%m%d_%H%M%S).png
# 3. Wayback Machine
waybackpy --url "https://scam-site.com" --save
# 4. Hash the evidence
sha256sum evidence_*.html screenshot_*.png > evidence_hashes.txtAdd to evidence_log.md:
| 2024-01-15 10:30:00 UTC | Archive | Scam homepage capture | abc123... | monolith |-
Executive Summary
- Case overview
- Key findings
- Recommended actions
-
Investigation Targets
- All identifiers investigated
- Connection between identifiers
-
Detailed Findings
- Per-identifier results
- Tool outputs
- Analysis notes
-
Evidence Inventory
- File list with hashes
- Chain of custody log
-
Abuse Contacts
- Registrar
- Hosting provider
- ISP
-
Recommendations
- Abuse reports to file
- Law enforcement referral
- Client advisories
From investigation, compile:
- Domain registrar abuse email
- Hosting provider abuse email
- Email provider abuse address
- Upstream ISP (if identifiable)
Use template from toolkit:
./osint_investigator.sh โ Reports Menu โ Generate Abuse Report Template
Include:
- Nature of abuse (phishing, scam, malware)
- Specific URLs/IPs/domains
- Timeline of activity
- Evidence (references, not attachments)
- Your contact information
Domain Registrar:
- Submit via registrar's abuse portal
- Reference domain name
- Request suspension/takedown
Hosting Provider:
- Email to abuse contact from ASN lookup
- Include IP addresses and URLs
- Request content removal
Email Provider:
- Forward original scam email
- Report via provider's abuse form
- Request account termination
Record in case file:
- Date/time of submission
- Recipient
- Method (email, web form)
- Reference/ticket number
- Attachments sent
- Wait 48-72 hours for initial response
- Follow up if no response
- Document all communications
- Escalate if necessary
For FBI Internet Crime Complaint Center (ic3.gov):
- Victim information
- Suspect information (all identifiers)
- Financial loss amount
- Payment methods used
- Communication records
- Investigation report (PDF)
- Evidence hashes
- Timeline of events
Submit at: https://www.ic3.gov/
Document version: 1.0 Last updated: 2024
- README.md - Playbook index
- ../OSINT_CHEATSHEET.md - Quick command reference during investigation
- ../scripts/Domain_IP_Recon.md - Automated domain investigation
- ../scripts/Email_OSINT.md - Automated email investigation
๐ Source: OSINT/Playbook/investigation_guide.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Open Source Intelligence (OSINT)
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics