Repository navigation
EmailOSINT AgentFlow
AnythingLLM AgentFlow for email address OSINT - investigates a target email address across public data sources to identify associated accounts, social profiles, breach exposure, and likely identity.
Accepts an email address, queries public OSINT sources (breach databases, social media, public records, search engines), and returns: associated accounts/profiles, breach exposure, phone/name correlations, and confidence ratings.
Build a profile on a target email address for authorized social engineering research, insider threat investigation, or engagement scoping.
Investigating a phishing sender's email; profiling an email address during authorized engagement recon; correlating email addresses to real identities for red team targeting.
Name: EmailOSINT
Description:
Investigates email addresses or usernames across multiple platforms to find accounts,
breaches, and public information for social engineering assessments.
Purpose: Email address intelligence and breach verification
Define these variables in the "Flow Variables" section:
| Variable Name | Initial Value | Description |
|---|---|---|
email_or_username |
(empty) | Target email address or username |
haveibeenpwned_data |
(empty) | Breach data from HIBP |
social_media_data |
(empty) | Social media search results |
breach_summary |
(empty) | Analyzed breach information |
social_profile |
(empty) | Social media profile analysis |
final_report |
(empty) | Complete intelligence report |
Block Type: API Call
Configuration:
- Method: GET
-
URL:
https://haveibeenpwned.com/api/v3/breachedaccount/${email_or_username} -
Headers:
{ "hibp-api-key": "YOUR_HIBP_API_KEY", "user-agent": "PenTest-Research" } -
Result Variable:
haveibeenpwned_data
Purpose: Check if email appears in known data breaches
API Key: Get free key at https://haveibeenpwned.com/API/Key
Note: HaveIBeenPwned requires API key for automated queries
Block Type: Web Scraping
Configuration:
-
URL:
https://www.google.com/search?q="${email_or_username}"+site:linkedin.com+OR+site:twitter.com+OR+site:facebook.com - Capture Page Content As: Text content only
- Content Summarization: Enabled
-
Result Variable:
social_media_data
Purpose: Find associated social media accounts
Alternative URLs:
https://www.google.com/search?q="${email_or_username}"+site:github.comhttps://www.google.com/search?q="${email_or_username}"+inurl:profile
Block Type: LLM Instruction
Instruction:
Analyze breach data for ${email_or_username}:
${haveibeenpwned_data}
Provide comprehensive breach analysis:
## Breach Summary
- Total number of breaches found
- Most recent breach date
- Oldest breach date
## Breached Services
List each breached service with:
- Service name
- Breach date
- Number of accounts affected
- Severity level
## Data Types Exposed
Categorize exposed data:
- Passwords (hashed/plaintext)
- Email addresses
- Personal information (names, addresses, phone)
- Financial data
- Security questions/answers
- IP addresses
- Other sensitive data
## Risk Assessment
- Password reuse risk level (High/Medium/Low)
- Account takeover likelihood
- Identity theft potential
- Social engineering implications
## Recommendations
- Immediate actions required
- Account security improvements
- Monitoring suggestions
Format professionally for security assessment report.
Result Variable: breach_summary
Purpose: Analyze and contextualize breach data
Block Type: LLM Instruction
Instruction:
Analyze social media presence for ${email_or_username}:
${social_media_data}
Extract intelligence:
## Confirmed Social Media Accounts
List each identified account with:
- Platform (LinkedIn, Twitter, Facebook, GitHub, etc.)
- Profile URL (if found)
- Account status (active/inactive)
- Verification status
## Public Information Shared
Identify publicly visible information:
- Personal details (location, birthday, relationships)
- Professional information (employer, job title, skills)
- Interests and activities
- Connections and associations
- Photos and media
- Contact information
## Security Awareness Indicators
Assess target's security posture:
- Privacy settings (public vs. private)
- Information oversharing
- Security-related posts or discussions
- Technology literacy indicators
- Security tool usage mentions
## Social Engineering Opportunities
Identify potential vectors:
- Topics of interest for phishing themes
- Trusted contacts/relationships
- Behavioral patterns
- Emotional triggers
- Professional concerns
## OPSEC Assessment
- Information disclosure rating
- Privacy consciousness
- Digital footprint size
- Security awareness level
โ ๏ธ Note: Use only for authorized security assessments
Result Variable: social_profile
Purpose: Create social engineering intelligence profile
Block Type: LLM Instruction
Instruction:
Create comprehensive email/username intelligence report:
Target: ${email_or_username}
Breach Data: ${breach_summary}
Social Media Intelligence: ${social_profile}
Format as professional OSINT report:
# OSINT Intelligence Report
## Target: ${email_or_username}
### Executive Summary
[Brief overview of findings and risk level]
### Breach History
${breach_summary}
### Social Media Presence
${social_profile}
### Overall Security Posture
[Assessment of target's security awareness and digital hygiene]
### Social Engineering Vectors
[Potential attack methods based on gathered intelligence]
### Recommendations for Testing
[Suggested approaches for authorized social engineering assessment]
### Defensive Recommendations
[If reporting to target: steps to improve security posture]
---
*Report generated for authorized security assessment*
*Date: [Current date]*
Result Variable: final_report
Purpose: Compile all intelligence into deliverable format
Block Type: Flow Complete
Configuration:
- Flow will end here and return results
@agent use EmailOSINT flow
email_or_username: john.doe@target.com
@agent use EmailOSINT flow
email_or_username: johndoe
The flow will return final_report containing:
- Complete breach history with data exposed
- Social media account discovery
- Public information analysis
- Security awareness assessment
- Social engineering opportunities
- Recommendations
Typical Workflow:
- CompanyOSINT - Identify key personnel and email formats
- EmailOSINT (this flow) - Investigate specific individuals
- BreachChecker - Cross-verify breach data
- GitHubSecrets - Check for code commits under username
Social Engineering Assessment:
- CompanyOSINT โ Get target list
- EmailOSINT โ Profile each target
- Compile social engineering strategy
Required for Block 1
- Visit: https://haveibeenpwned.com/API/Key
- Subscribe ($3.50/month as of 2025)
- Receive API key via email
- Add to flow: Replace
YOUR_HIBP_API_KEYwith actual key
Rate Limits:
- 10 requests per minute with API key
- Respect rate limits to avoid blocking
Replace Block 1 with web scraping:
Block Type: Web Scraping
URL: https://haveibeenpwned.com/account/${email_or_username}
Capture: Text content only
Result Variable: haveibeenpwned_data
Note: May be blocked or require CAPTCHA
Add Block for Paste Sites:
Block Type: API Call
Method: GET
URL: https://haveibeenpwned.com/api/v3/pasteaccount/${email_or_username}
Headers: {"hibp-api-key": "YOUR_KEY"}
Result Variable: paste_data
Add Block for DeHashed (requires subscription):
Block Type: API Call
Method: GET
URL: https://api.dehashed.com/search?query=email:${email_or_username}
Headers: {
"Accept": "application/json",
"Authorization": "Bearer YOUR_DEHASHED_KEY"
}
Result Variable: dehashed_data
โ ๏ธ Authorization Required - Only use with written permission- Privacy Laws - Respect GDPR, CCPA, and local privacy regulations
- Data Handling - Secure storage and proper disposal of PII
- Purpose Limitation - Use only for authorized security assessments
- Informed Consent - Target organization must authorize investigation
- False Positives - Common names/usernames may return unrelated results
- Rate Limiting - HIBP has request limits even with API key
- Google CAPTCHA - Social media search may trigger CAPTCHA
- Account Privacy - Private social media accounts won't show details
- PII Handling - Treat discovered information as confidential
- Report Security - Encrypt reports containing personal data
- Retention - Follow data retention policies
- Disclosure - Report findings only to authorized parties
-
Try Variations:
- email@domain.com
- email+tag@domain.com
- Alternative email formats
-
Cross-Reference:
- Check multiple breach databases
- Verify findings with target
- Look for credential reuse patterns
-
Use Multiple Search Engines:
- Bing
- DuckDuckGo (privacy-focused)
-
Try Different Search Queries:
"email" site:linkedin.com"username" profile"firstname lastname" company
-
Check Additional Platforms:
- GitHub (developer profiles)
- Stack Overflow (technical users)
- Reddit (usernames)
- Medium (bloggers)
| Issue | Solution |
|---|---|
| HIBP returns no data | Email may not be breached; verify email is correct |
| API authentication fails | Check API key is valid and properly formatted |
| Social media search blocked | Google CAPTCHA triggered; try manual search |
| Too much irrelevant data | Use more specific search terms or filters |
| Generic analysis | Provide additional context about target |
| Rate limit exceeded | Wait 1 minute between requests for HIBP |
After running EmailOSINT:
- Verify Findings - Confirm breach data is accurate
- Document Results - Add to engagement documentation
- Assess Risk - Determine if passwords should be tested
- Report Responsibly - Notify client of serious exposures
- Update Target List - Refine social engineering targets
- Identify compromised credentials for password spraying
- Build social engineering pretexts
- Discover forgotten accounts
- Map target's digital footprint
- Demonstrate breach exposure to employees
- Educate on password reuse risks
- Show social media oversharing consequences
- Investigate compromised accounts
- Track attacker email addresses
- Correlate breach timelines
- Profile high-value targets
- Craft convincing phishing campaigns
- Identify trust relationships
- v1.0 - Initial flow with HIBP and social media search
- Purpose: Email intelligence for authorized assessments
- Last Updated: November 2025
- CompanyOSINT - Identify target emails
- BreachChecker - Domain-wide breach checking
- GitHubSecrets - Username code search
- VulnReportGenerator - Document findings
- README.md - AnythingLLM AgentFlow index
- flow-breacher_check.md - Breach checking as a sub-step of email OSINT
- flow-company_osint.md - Company context for corporate email addresses
- anything_llm_agentflows.md - Email OSINT in the standard recon chain
๐ Source: AI/AnythingLLM/flow-email_osint.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Artificial Intelligence
- ๐บ๏ธ 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