Scanners
Scanners allow you to set up automated monitoring of stealer logs. When new credentials matching your search criteria are indexed, you’ll receive notifications via email, Discord webhook, or HTTP webhook.How Scanners Work
Important: Scanners only find new data indexed after the scanner is created. They search using
indexed_at date starting from when you created the scanner. To find existing data, use the regular search on OathNet.- Hourly Scanning: Scanners run automatically every hour
- Incremental Search: Only searches for results indexed since the last run
- Multiple Notification Types: Email, Discord, or custom HTTP webhook
- Plan-Based Limits: Higher plans get more scanners
Scanner Limits by Plan
Each plan includes a different number of scanners. Check your plan details on the Pricing Page for current limits. You can view your remaining scanner quota in Dashboard → Notifier (shown as “X/Y scanners” in the header).Creating a Scanner (Dashboard UI)
- Go to oathnet.org/dashboard
- Click the Notifier tab
- Click New Scanner
- Fill in the form:
Scanner Name
A friendly name to identify your scanner (e.g., “Company Domain Monitor”).Query Filters
Add at least one filter to monitor. When new stealer logs matching your filters are indexed, you’ll be notified.| Filter | Description | Example |
|---|---|---|
| Domains | Monitor credentials from specific domains | example.com |
| Subdomains | Monitor specific subdomains | mail.example.com |
| Usernames | Monitor specific usernames or emails | [email protected] |
| Passwords | Monitor specific password patterns | Summer2024! |
| Paths | Monitor specific URL paths | /admin/login |
| Log ID | Monitor a specific stealer log (Advanced) | abc123... |
Notification Method
Choose how you want to be notified:| Method | Description |
|---|---|
| Sends to your account email with results summary and link | |
| Discord Webhook | Posts a rich embed to your Discord channel |
| Custom Webhook | Sends JSON payload to your own endpoint |
Webhook URL
Required for Discord and Custom Webhook notifications.- Discord: Get your webhook URL from Discord Server Settings → Integrations → Webhooks
- Format:
https://discord.com/api/webhooks/{id}/{token}
- Format:
- Custom: Any HTTPS URL that accepts POST requests
- Must use HTTPS (not HTTP)
- Must be a domain name (IP addresses not allowed)
Notify on Zero Results
When enabled: You’ll receive a notification every time the scanner runs, even if no new results are found. Useful for confirming your webhook is working. When disabled (default): You’ll only receive notifications when new matching results are found. Recommended for production use to avoid notification spam.Scanner Actions
Test Notification
Click Test to send a test notification to verify your webhook is configured correctly. This sends a test payload without running an actual search.Run Now
Click Run Now to manually trigger the scanner immediately instead of waiting for the next hourly run.Pause / Resume
Temporarily pause a scanner without deleting it. Paused scanners won’t run until resumed.View Details
See scanner run history, including:- When each run occurred
- How many results were found
- Notification delivery status
Webhook Payload Format
When using Custom Webhook, you’ll receive this JSON payload:Content-Type: application/jsonUser-Agent: OathNet-Scanner/1.0X-Scanner-UID: <scanner-uuid>
scanner.results_found- Real results foundscanner.test- Test notification
Replicating Scanner Behavior via API
If you want to build your own scanner logic using the API, you can replicate the scanner behavior by using theindexed_at date filter.
Example: Search for new stealer logs since a specific date
from- Search for results indexed after this date (ISO 8601 format)date_field=indexed_at- Filter by when OathNet indexed the result (not when it was originally compromised)
from date for the next search.
Example Webhook Handlers
Node.js
Python
Troubleshooting
No results found
- Scanners only find new data indexed after creation
- Use the regular search to find existing data
- Make sure your filters aren’t too restrictive
Not receiving notifications
- Check if “Notify on Zero Results” is enabled (for testing)
- Use “Test” button to verify webhook is working
- Check scanner run history for notification errors
- Ensure webhook URL is HTTPS and responds with 2xx status
Scanner disabled
- Scanners are auto-disabled after 5 consecutive failures
- Check if your plan still allows scanners
- Re-enable from the scanner details page
Scanner Management API
Coming Soon: Scanner API access via API key is not yet available. Currently, scanners can only be managed through the OathNet Dashboard. API support will be added in a future update.