How to Secure Your Gosuslugi Account Against Hacks and Recover Access After Takeover
Russia's Gosuslugi portal serves as a central hub for official documents, tax notifications, child records, data-sharing consents, and access to numerous other government services. A compromised account can lead to fraudulent applications, altered contacts, unauthorized consents, and even financial risks such as loans taken in the victim's name.
Strengthen Login Protection Beyond a Single Password
Users should always access the portal directly at gosuslugi.ru rather than through links in messages. In the Profile section under Security and Login, enable an additional verification method. Recommended options include TOTP one-time codes from an authenticator app or biometrics, as SMS codes remain vulnerable to SIM swapping. After setup, save backup TOTP codes in a secure location and verify the change by logging out and back in.
The linked phone number also requires protection. Immediately block a lost SIM card with the mobile operator and review active sessions in important services. Regular checks of the Security section help identify unknown logins, devices, or changes.
Review Connected Devices, Consents, and Trusted Contacts
Within Profile and Security, examine recent actions, mobile applications, and granted consents. Remove old phones, unknown devices, and unnecessary permissions. Add a trusted contact who can assist with recovery without gaining account access. Control questions should use answers not available in public data.
The Consents section deserves special attention after any suspicious activity. Review each permission for validity, revoke unknown ones, and keep screenshots as evidence.
Respond to Unexpected Codes or Suspicious Calls
An unsolicited verification code almost always signals an attempted login. Do not reply, click links, or share the code. Instead, manually open the official site, change the password, and audit all sections. Support staff, banks, or police never request codes, passwords, or personal data over the phone to verify an account.
Recover Access and Mitigate Damage After a Breach
If the account is already compromised, first change the password and end foreign sessions if possible. Use the recovery page with passport, INN, or SNILS details, or visit a service center in person. After regaining access, verify all personal data, statements, and consents, then secure the linked email and phone account.
Request a credit report and consider placing a self-ban on consumer loans through Gosuslugi starting March 2025 or MFC from September 2025. The ban covers most credit products but excludes mortgages and certain educational loans, and it cannot be lifted instantly.
Prevent Social Engineering Attacks
Most attacks begin with phone calls claiming urgent issues such as fines, blocked accounts, or suspicious activity. Never share codes or install remote-access software. Always verify requests independently by visiting official websites directly. Store records of suspicious messages for potential reports to the Ministry of Internal Affairs.
Related articles
T-Bank's wev.js Anti-Fraud Collector: Reverse Engineering Browser Fingerprinting for Bot Detection
A detailed reverse engineering of T-Bank's wev.js anti-fraud SDK reveals how the bank builds a persistent device fingerprint during debit card applications. The collector draws an invisible 2000x200 canvas with non-existent fonts and colored arcs, then hashes the result with SHA256 to create a stable device identifier called nf. It also captures twelve data blocks including compressed mouse and keyboard event streams, full WebGL renderer details such as UNMASKED_RENDERER exposing the Apple M4 Max chip, and sensor data from gyroscopes and accelerometers. Eight dedicated bot-detection checks target automation frameworks by inspecting navigator.webdriver, native code descriptors, and Safari-specific markers. Experiments showed that spoofing the GPU renderer leaves the nf hash unchanged, while deterministic canvas modifications can create a stable fake device fingerprint. A second collector, fp-pixel.js, runs on SSO pages and aggregates even more signals including audio, fonts, and WebRTC before sending data to a separate endpoint.
Scammers Impersonate Russian Traffic Police and Treasury Demanding Repeat Fine Payments
Russian scammers are sending SMS messages impersonating the State Traffic Inspectorate and the Federal Treasury, claiming that previous payments for traffic fines or state fees were not processed due to a system update. Recipients are instructed to pay the amount again or a small confirmation fee through a phishing link, with threats of accumulating debt if they refuse. The scheme was reported by the Moshilovka platform operated by the Narodny Front. Official agencies do not request repeated payments via third-party links or charge fees for transaction confirmations. Users are advised to verify payment status only through a verified Gosuslugi account and retain electronic receipts for any fees paid.
Scammers Abuse Google Looker Studio to Send Fraudulent Compensation Emails
Kaspersky researchers have identified a new wave of Russian-language phishing emails distributed through the legitimate Google Looker Studio service, formerly known as Google Data Studio. The messages promise compensation payments or confirm supposedly approved money transfers from financial institutions, using the platform’s scheduled report delivery feature to reach victims. Emails arrive from a genuine Google address and carry the official Data Studio branding, making them harder for security tools to block. Recipients are directed to open documents in Google Presentations or forms in Google Forms that reference fake legal changes and display state symbols before leading to scam sites. The campaign is limited to messages sent at the start or middle of each hour due to scheduling constraints in the service. Experts note that the abuse of trusted platforms increases the difficulty of automated detection and filtering.
Human-like Cursor Movements: Evading Behavioral Anti-Fraud Detection in Browser Automation
Anti-detect browser provider Aurorium explains how modern anti-fraud systems analyze mouse telemetry including coordinates, timestamps, velocity profiles, acceleration, curvature, and USB polling intervals to distinguish humans from automated scripts. Standard straight-line movements at constant speed with perfect center clicks trigger immediate alerts because they lack natural human motor patterns described by Fitts's law. The article details four key techniques to simulate realistic behavior: cubic Bezier curves with random control points for organic arcs, phased acceleration and deceleration with occasional overshoot, low-amplitude Gaussian jitter that fades near targets, and offset clicks distributed around element centers. It also stresses that JavaScript click() calls set the isTrusted flag to false, making server-side mouse events via Playwright or Puppeteer mandatory. A complete Python implementation using Playwright's page.mouse API is provided, incorporating normal distribution sampling and smoothstep easing. The guide concludes that realistic mouse mechanics must be combined with clean residential proxies and consistent browser fingerprints to remain undetected.