known_phish() function tests your network’s ability to detect and block access to active phishing websites. It uses the OpenPhish community feed, which contains URLs of verified phishing sites updated in real-time.
Data Source
This module uses the OpenPhish community threat feed:- OpenPhish Feed -
https://openphish.com/feed.txt
OpenPhish provides a continuously updated list of verified phishing URLs. The feed contains hundreds to thousands of active phishing sites targeting various brands and services.
How It Works
1
Download Phishing Feed
Downloads the latest phishing URL list from OpenPhish.
2
Random URL Selection
Randomly selects 15 URLs from the feed and validates them using URL pattern matching.
3
HTTP Connection Testing
Attempts HTTP GET requests to each phishing URL with a 5-second timeout.
4
Results Logging
Logs all connection attempts with timestamps to
URL_Results.txt, indicating success or failure.5
Cleanup
Removes the temporary downloaded feed file after testing completes.
Output Format
Results are saved to URL_Results.txt with the following format:What to Monitor
Web Filtering
Your web proxy or content filter should block access to these phishing URLs before connections complete.
DNS Security
DNS security services should prevent resolution of known phishing domains.
URL Reputation
Security gateways should flag these URLs based on reputation scores and threat intelligence.
User Alerts
Endpoint security solutions should warn users if they attempt to access these sites.
Common Phishing Targets
OpenPhish feed typically includes phishing campaigns targeting:- Financial institutions (banks, payment processors)
- Cloud service providers (Microsoft, Google, AWS)
- Social media platforms
- E-commerce sites
- Cryptocurrency exchanges
- Email providers
Testing Workflow
The test attempts to connect to 15 random phishing URLs from the live feed. Some URLs may be offline or taken down, which is expected behavior and will show as FAILED.
Integration with Security Tools
Use this test to validate:- Web Application Firewalls (WAF) - Should block HTTP requests to known phishing domains
- Secure Web Gateways (SWG) - Should categorize and block phishing sites
- DNS Filtering - Should prevent DNS resolution of phishing domains
- Email Security - Should flag these URLs if found in email messages
- Endpoint Protection - Should prevent browsers from accessing these sites