Psychological Manipulation Outpaces Technical Hacks in Modern Cyber Scams
Many cyber incidents begin not with sophisticated code but with carefully crafted emotional pressure that bypasses rational decision-making. Users who intended only to compare prices suddenly complete purchases because a countdown timer claims the discount ends in minutes. Employees accept extra tasks to avoid appearing disloyal, while relatives forward alarming messages without verifying links. In each case the core question remains the same: did the person truly choose the action or simply seek relief from discomfort?
Manipulation does not always require falsehoods. A real price cut, a genuine team problem, or an authentic request can still become coercive when fear, shame, or artificial deadlines prevent evaluation of alternatives. The article distinguishes ordinary requests from pressure by observing how the other party reacts to questions or refusals. Reasonable counterparts clarify constraints and explore options; manipulators escalate demands and question the recipient’s character.
Fear as a Shortcut to Compliance
Messages that announce account compromise followed immediately by instructions to share codes combine two separate claims. The danger may exist, yet the prescribed remedy requires separate validation. Instead of verifying the threat through official channels, recipients rush to execute the suggested steps for emotional relief. Effective checks separate confirmation of the risk from confirmation that the proposed action actually mitigates it.
Guilt and False Urgency
Phrases such as “normal parents do not skimp on children” or “the team counted on you” shift discussion from the request to personal integrity. When refusal prompts moral accusations rather than negotiation, pressure is present. Similarly, countdown timers on checkout pages divert attention from delivery terms, hidden subscriptions, and return policies. Recording the final amount and comparing multiple offers before the timer expires helps restore perspective.
Recognizing and Resisting Combined Tactics
A single message may layer urgency, restricted communication channels, and appeals to loyalty. In such cases the priority is independent verification through previously known contact methods rather than replying inside the suspicious thread. Pre-prepared neutral responses allow recipients to state limits without debating their own motives.
After any unwanted action, further transfers or data sharing should stop immediately. Contact banks and organizations only through official applications or printed card numbers, and report incidents to law enforcement when money is lost. The goal is not perpetual suspicion but a consistent habit of verifying claims before irreversible steps are taken.
Related articles
Russian Minister Proposes Blocking All SIM Cards of Scammers Banned in MAX Messenger
The head of Russia's Ministry of Digital Development has suggested expanding account bans in the MAX messenger to include full disconnection of all mobile numbers belonging to the same owner. Maksut Shadaev stated that simply restricting the messenger account is insufficient and that operators must continue countermeasures. The proposal also includes a cooling-off period preventing the individual from registering new numbers after a ban. Details on the duration of restrictions, data transfer procedures to operators, and appeal mechanisms remain undisclosed. Questions around accurate owner identification and cases of compromised or misused numbers are highlighted as critical for implementation. The measures target fraudsters specifically and would not apply automatically to every MAX rule violation.
Avito Develops Cyberdetective Browser Game to Train Employees on Real-World Attacks Using MITRE ATT&CK Techniques
Avito security awareness specialist Ilya Nikiforov created the browser-based Cyberdetective game over 74 days to move beyond traditional courses and train practical responses to attacks. The game places players in the fictional company Lumi where they control mascot Spok the honey badger, investigating six cases based on authentic attack chains documented in MITRE ATT&CK. Scenarios cover physical access via unlocked laptops, invoice domain spoofing, voice cloning of executives, MFA fatigue attacks, and evidence preservation during incident response. The project relied heavily on AI agents including Claude Code and Codex for coding and testing while Nikiforov handled scenario design, methodology, and acceptance. Additional AI tools generated art, animations, voiceovers, and music, resulting in 80 JavaScript modules, roughly 2,200 automated tests, and 18 distinct interactive mechanics. The game emphasizes safe mistake-making, chain-of-events thinking, and specific actions such as callback verification rather than blanket refusal of all requests.
Scammers Use *#62# USSD Command to Fabricate Surveillance Claims and Steal Victims' Funds
Fraudsters are exploiting the USSD command *#62# to convince targets that their phones are being tapped, then directing them to hand over cash to supposed couriers. The scheme begins with a familiar pretext such as a doorphone replacement or parcel delivery, after which the victim is tricked into revealing a verification code that the attackers themselves sent. A fake government official then claims the victim's account has been compromised and an extremist has been granted power of attorney. Victims are instructed to visit a counterfeit state website, enter *#62#, and interpret the displayed forwarding number as proof of interception. In reality the code only reveals call-forwarding settings for when the phone is unreachable, often showing a voicemail or missed-call service number. T-Bank warns that the displayed number has no connection to surveillance and urges anyone receiving such calls to hang up and contact the real organization through official channels.
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.