Russian security vendor Security Code (Код Безопасности) has published findings on a large criminal campaign against the finance and accounting teams of Russian organisations. The report, covered on 10 August 2026 by Anti-Malware.ru, Gazeta.Ru and other Russian outlets, says losses in the first half of 2026 exceeded 4 billion rubles.
What happened
- More than 3,000 organisations were targeted, including government bodies, industrial companies, financial institutions and telecom operators.
- About one in eight attacks succeeded, giving the attackers control of roughly 400 accountants’ workstations.
- In March and April the average loss per incident reached about 10 million rubles.
How the attacks work
Phishing was the main way in. Lures were tailored to each victim’s role and organisation, and malicious attachments were disguised as everyday finance paperwork such as invoices, contracts, waybills and reconciliation statements. Messages arrived by email and through messengers, often posing as instructions from a manager or counterparty.
Once inside, the operators worked within legitimate, authenticated user sessions and watched the cryptographic tokens used for remote banking. Instead of moving money straight away, they often waited for months. During that time they studied the network, reached backups, weakened security tools and disguised their activity as routine IT administration.
Security Code also notes two wider trends:
- Supply-chain entry: weaker contractors were compromised to reach larger customers, using legitimate accounts, remote-access tools and even official update channels.
- Cloud abuse: cloud services were used to host attack components, relay commands and exfiltrate data.
According to the report, about 40% of targeted intrusions against industry, government and critical infrastructure in Q1 2026 aimed at intelligence gathering. Targets included technical documentation, production capacity data, R&D results and internal correspondence.
Recommendations
- Separate the workstations used for remote banking from general email and messenger use, and store signing keys on hardware tokens that are disconnected when not in use.
- Require out-of-band confirmation for new payees and for payment instructions received by email or messenger.
- Monitor finance endpoints for unexpected remote-access tools and long-lived sessions outside working hours.
- Review contractor access and update channels as part of third-party risk management.
- Remember that backups restore operations but cannot undo data theft, so detection matters as much as recovery.