Securitylab•July 20, 2026•🇷🇺Translated from Russian

Protecting Your Credit History: How to Check for Unauthorized Microloans and Set Up Self-Bans in Russia

Russians typically learn about loans taken out in their name only after a bank refuses a new card or loan, at which point an unfamiliar debt appears in their credit report. Checking your credit history can be done online and free of charge. First, identify which credit bureaus hold your data, then download the reports and carefully examine all contracts, applications, and creditor requests instead of stopping at the credit score. If you do not plan to take out loans soon, it makes sense to immediately place a self-ban, which makes it significantly harder for fraudsters to obtain credit using your personal data.

Where to Check Your Credit History

There is no single centralized database. Banks, microfinance organizations, and other lenders send data to different credit bureaus, and it is impossible to know in advance which ones hold your information. The list of bureaus storing your credit history is provided by the Central Catalogue of Credit Histories (CCCH) of the Bank of Russia.

Through Gosuslugi, the entire process takes just a few minutes. Open the service for obtaining information from the CCCH, verify your passport details, submit the request, and receive the list of bureaus. Without a Gosuslugi account, you can use the Bank of Russia section “How to find out your credit history,” though this requires a credit history subject code.

Obtain bureau addresses from the official state register maintained by the Bank of Russia, as the list changes periodically and search engines may return outdated information. While major players such as NBKI and United Credit Bureau are well-known, you must check every bureau listed in the CCCH response. In each bureau’s personal account, download the report in PDF format. The electronic version is free twice a year, while the paper version is available once.

What to Look for in Your Credit Report

The credit score reduces your entire history to a single number and explains nothing. Protection against fraud comes from other sections that list contracts, applications, and creditor inquiries. These sections show who accessed your history, which contracts remain open, and where delinquencies exist. For every entry, verify the creditor, date, amount, obligation number, and last update date.

An unfamiliar microloan of just a few thousand rubles is not a minor issue, as fraud chains often begin with small amounts. Pay special attention to the inquiries block. If multiple lenders requested your report on the same day without your involvement, change passwords immediately, check Gosuslugi, and activate a self-ban.

What was foundWhat it meansWhat to do
Unknown loan or microloanFraud or errorSave the report, contact the creditor, file a police report
Multiple MFO applications in one daySomeone was shopping for a loanCheck accounts, SIM card, email, enable self-ban
Closed loan still shown as activeCreditor failed to update dataRequest closure certificate and dispute the record
Delinquency that never occurredPayment accounting errorPrepare receipts and request correction
Inquiry from unknown creditorApplication made without your participationCheck all bureaus and change passwords

Self-Ban on Loans: How to Activate It and When It Helps

A self-ban is recommended for anyone who does not intend to take out credit or microloans in the near future. From 1 March 2025, it can be issued via Gosuslugi; from 1 September 2025, also through MFC. After submission, a mark appears in your credit history, and banks and MFOs must reject applications while the ban remains active.

If a lender issues funds despite an active ban, the contract is concluded in violation of the law. The creditor acquires no rights to demand repayment, the borrower is not obliged to return the money, and the record is removed from the history even if the debt has already been sold.

Through Gosuslugi you can choose a full or partial ban. A full ban blocks consumer loans and borrowings from banks and MFOs. A partial ban can be configured more precisely, for example, prohibiting only remote applications while allowing in-person applications at branches. Mortgages, car loans secured by the vehicle, state-supported education loans, suretyship, transactions on already opened cards, and repayment of existing debts are not covered. Existing loans do not need to be closed to activate the self-ban.

The ban takes effect the day after the mark appears in the history, and it can only be lifted on the second calendar day Moscow time. This one- or two-day pause disrupts telephone scams that pressure victims into making “safe” transfers or urgent loans before they change their minds.

Pre-Travel Security Checks

During travel, control over documents and communications weakens. Passport scans may be sent in chats, phones can be lost, and hotel Wi-Fi is often open. The Russian self-ban does not apply to foreign banks, but access to domestic banks, Gosuslugi, and SIM cards remains vulnerable. After intercepting these, fraudsters can operate remotely regardless of your physical location.

Before departure, download your credit reports, activate a self-ban, and enable bank notifications. Verify logins to Gosuslugi, email, and banks. For international travel, confirm that SMS messages arrive in roaming. Review the security section of Gosuslugi for activity history and close unknown sessions. Do not leave passport scans in open chats. Avoid accessing credit bureaus, banks, or Gosuslugi from other people’s devices or unsecured Wi-Fi. If you lose your passport, immediately report it to the police and keep the confirmation. If your phone is lost, block the SIM card and active sessions, then download a fresh report upon return.

What to Do If Fraudsters Have Already Taken Out a Loan

Disputes are won with documents, not phone calls to call centers. The earlier written evidence appears, the stronger your position.

  • Download reports from all your credit bureaus, save the PDFs and screenshots of disputed entries, and note the creditor, contract date, amount, and obligation number.
  • Submit a written statement to the creditor denying the contract and receipt of funds, and request an investigation including signing method, phone number, disbursement details, and IP addresses. If you were in another city that day, attach tickets, bookings, and receipts.
  • File a police report in person at an МВД department, via the agency’s website, or by calling 102 (not 112, which is for emergencies). Keep the notification coupon.
  • Dispute the record through the credit bureau free of charge. The bureau must provide a reasoned response within 20 working days; direct contact with the creditor requires a response within 10 days.
  • If the creditor remains silent, file a complaint via the Bank of Russia internet reception. If enforcement proceedings begin, check the FSSP database of enforcement proceedings.

Note that the FSSP database does not show recent loans and applications; it is useful only after the dispute reaches court or enforcement proceedings.

Paying someone else’s debt “to make them stop” is tempting but almost always harmful. Payment complicates the dispute and may be viewed by the creditor as acknowledgment of the debt. Written statements and persistent correction of the record are far more effective.

Protection Checklist

Credit fraud rarely relies on a single vulnerability; usually several gaps coincide. Therefore, protection depends on consistent habits rather than one-time settings.

  • Check your credit history twice a year at every bureau and additionally after losing a passport, phone, or SIM card.
  • Activate a self-ban if you do not currently need credit.
  • Use different passwords for email, Gosuslugi, banks, and mobile operators, and enable two-factor authentication everywhere it is available.
  • Periodically review the Gosuslugi security section and activity history.
  • Never dictate SMS codes or card details over the phone or send passport photos to unverified chats.
  • Store document copies in a secure location and update bank records immediately after changing your passport.

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.