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

Why 'Be Vigilant' Is Not Enough: Dissecting Human Psychology During Social Engineering Attacks

A cybersecurity specialist with extensive experience in SOC operations and penetration testing argues that the most expensive perimeter breaches rarely occur through code vulnerabilities. They happen through the person sitting behind that perimeter. Firewalls do not get tired, do not want to please management, and do not feel fear. Humans do.

This analysis focuses on the mechanics of what happens to a person at the moment of a social engineering attack and why standard awareness briefings provide little protection. The author stresses that social engineering does not target vices but rather positive traits such as politeness, willingness to help, and respect for authority.

Why vigilance fails under pressure

Standard responses to social engineering involve presentations and posters urging employees to “be vigilant.” Within weeks the same employees fall for the same tactics. The training lives in the conscious layer of the mind, while attacks operate by forcing automatic responses. Under time pressure and perceived authority, employees stop asking clarifying questions. The same person who would spot inconsistencies in a written request without time constraints will approve it when rushed.

The practical conclusion is that protection cannot depend on an individual’s willpower during their worst moment. It must rely on procedures that activate automatically.

Psychological levers attackers use

Attackers apply well-known mechanisms from social psychology:

  • Authority — confident tone and references to senior roles make employees reluctant to question requests, especially in hierarchical organizations.
  • Urgency — phrases such as “act immediately” or “account will be blocked in an hour” eliminate time for verification.
  • Reciprocity — attackers first “solve” a problem they created, creating a sense of obligation.
  • Social proof — claims that colleagues have already approved the action remove personal responsibility.
  • Sympathy and fear — emotional manipulation shifts the target from analytical thinking to emotional response.

All five levers target the same point: the willingness to take a pause. Effective defense must therefore protect that pause.

What actually works

Organizations should codify the right to pause in official procedures rather than presentations. Any urgent request involving money, access, or data must be confirmed through an independent channel. Employees must know they will not be punished for verifying requests, even when the caller claims to be the CEO. A culture that treats early error reporting as a positive action rather than a source of shame catches incidents early. Technical controls such as out-of-band confirmation codes and external-sender markings further reduce reliance on a single stressed individual.

The article concludes that security does not end at ports and patches. When psychological levers override procedures, the human element becomes the weakest link unless organizations deliberately design processes that think for employees when thinking becomes difficult.

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.