Developer Releases PhishIntel Open-Source Tool for Phishing Site Analysis and Risk Scoring
A developer has released PhishIntel, an open-source Python tool for automated OSINT analysis of websites and assessment of phishing risk. The project was created after the author encountered reports of fraudsters using the classic “Mammoth” scheme with the fake brand Toplivo24 to sell gasoline, gas, and diesel at 20–30% below market price through phishing sites, netting at least 3.7 million rubles in one week.
The application runs with standard Python libraries and produces a structured JSON report after executing a single command. Core modules examine domain composition for suspicious keywords and subdomains, retrieve DNS records (A, AAAA, MX, NS, TXT, CAA, SOA), perform reverse DNS lookups, and collect registration data via both RDAP and WHOIS. Additional checks cover TLS certificate details, HTTP response headers, redirect chains, HTML forms, input fields, external scripts, and the presence of protective headers such as HSTS, CSP, and Referrer-Policy.
Further analysis includes static examination of JavaScript files for risky patterns (eval, fetch, cookie access, obfuscation), retrieval of robots.txt and security.txt, sitemap parsing, and historical comparison of DNS and TLS observations stored in a local JSONL file. Subdomain discovery combines Certificate Transparency logs from crt.sh with brute-force enumeration using a provided wordlist.
When optional tools and API keys are supplied, the report expands to include reputation results from VirusTotal, Google Safe Browsing, and URLhaus, dynamic browser behavior captured via Playwright, and active scans performed by Nmap, Nuclei, or ZAP. A final risk-scoring module aggregates all findings into a numeric score and severity level (informational to critical) with explicit supporting evidence.
The author emphasizes that the code was intentionally kept simple to allow easy customization. The repository is available on GitHub under the name PhishIntel, and the developer welcomes technical feedback from security practitioners on both existing functionality and potential new features.
Related articles
Aroshka Cloud Faces Scrutiny Over Alleged False Claims of SOC 24/7 Operations and High-End Infrastructure
StackWorks has published the fourth installment in its investigative series on Aroshka Cloud, detailing how the cloud storage provider accused the studio of orchestrating a DDoS attack shortly after the third part appeared. The service published five posts claiming technical evidence linked StackWorks to the attack, including IP traces from Moscow, Ufa, and Stavropol, while asserting that its SOC 24/7 team mitigated a 3.5 Gbit/s assault within seconds. StackWorks responded with a pre-trial claim demanding removal of the posts and a public retraction, which Aroshka Cloud rejected within seven minutes. Analysis of the provider’s own Kwork job postings reveals requests for template-based support staff, a five-VDS server pool, and later up to eight NVIDIA H200 GPUs with InfiniBand, contradicting public statements about multi-country data centers and round-the-clock security engineers. Further inconsistencies include mismatched time zones in email headers, inflated user statistics, and reliance on the BeDrive script rather than custom development. The investigation continues with plans to involve law enforcement regarding suspicious visitor logs.
Reports Surface on Alleged De-Anonymization of Admins Running Major Russian Hacker Forums
An independent researcher has compiled publicly available information pointing to the possible identities of administrators behind prominent Russian-language darknet forums including exploit.in and duty-free.to. The analysis traces exploit.in back to its 2006 launch by a user known as Toha, later linked to Ukrainian authorities or associates, with the forum reportedly transferred or sold. Forum moderator Quake3, identified in open sources as Anatoly Kravchuk, ceased activity in October 2026 and appears on a German police wanted list. Additional details from forum posts and anonymous Telegram channels name Mikhail Rytikov, known as Abdulla, as a key figure tied to server hosting and operations. The report also notes the recent involvement of known Russian hacker wazawaka on duty-free.to and highlights the declining viability of several legacy forums due to law enforcement actions. All claims are presented as unverified public speculation without new original sourcing.
Google Strengthens Chrome Defenses Against ClickFix Clipboard-Based Scams
Google has updated Chrome to detect and warn users about malicious commands copied to the clipboard as part of ClickFix attacks. These scams trick users into pasting harmful scripts into system tools such as PowerShell under the guise of fixing errors or providing tech support. The new protections activate when Enhanced Protection in Safe Browsing is enabled and send suspicious commands for analysis after removing personal data. Google has also shifted scam page detection from a local Gemini model to a server-side implementation to improve accuracy against fake tech support, antivirus, and browser update sites. The changes make it harder for attackers to bypass browser download checks by abusing clipboard and system console execution. Official details were published in the Google Security Blog.
SPF, DKIM and DMARC: Practical Guide to Detecting Email Spoofing and Phishing
The article explains how email authentication mechanisms SPF, DKIM, and DMARC work together to combat spoofed messages that impersonate trusted services. It provides concrete DNS record examples and shows how to interpret Authentication-Results headers in received emails. SPF verifies authorized sending IP addresses but does not check the visible From address. DKIM adds cryptographic signatures to message content and headers, while DMARC ties these checks to the sender domain visible to users and defines handling policies. The guide also covers common configuration errors, forwarding issues, and why successful authentication does not guarantee message safety. It concludes that these protocols must be combined with additional security measures such as attachment scanning and user awareness training.