Habr•August 26, 2026•🇷🇺Translated from Russian

Email Graph Analysis Detects Impersonated Suppliers When DKIM and SPF Pass

Traditional email security controls such as DKIM, SPF, and DMARC fail when an attacker has already compromised a legitimate supplier mailbox. In these cases the message arrives from the genuine server, carries a valid signature, and continues an existing thread, leaving no technical anomaly to detect.

The only reliable signal lies in the historical pattern of communication between the two parties. Mail gateway logs already contain the necessary metadata: sender, recipient, and timestamp. No message bodies or attachments are required, which simplifies legal and privacy reviews.

From Postfix logs the pairs are extracted with simple shell commands that join queue identifiers. Microsoft Exchange environments provide the same data through the Get-MessageTrace cmdlet, which should be exported daily to accumulate sufficient history.

Each external-internal address pair is profiled with counts, first and last seen dates, inbound versus outbound volume, and hourly distribution. These numbers feed five lightweight indicators:

  • First contact – the address has never appeared before.
  • Lookalike known – the domain is similar to a previously observed supplier domain using a split name-zone comparison that ignores hyphens.
  • Dormant revived – communication resumed after more than 180 days of silence.
  • One-way traffic – dozens of inbound messages with zero replies.
  • Unusual hours – messages arrive outside the established working-hour pattern.

A weighted score combines the indicators so that no single weak signal triggers an alert. High scores can be surfaced as a banner inside the recipient’s mailbox or routed to the SOC for manual review.

The method breaks down for generic addresses such as info@ or sales@ and for organizations that receive fewer than several thousand external messages per day. In those environments the recommended minimum control remains a telephone callback to a known contract number before any banking details are changed.

Related articles

Habr•Fraud & Social Engineering

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.

Habr•Fraud & Social Engineering

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.

AntiMalware•Fraud & Social Engineering

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.

Habr•Fraud & Social Engineering

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.