
The unifying theme in June is trust, which is abused: old passwords, abandoned packages and plugins that we trust simply because they always worked. The month’s highlights include the “FortiBleed” incident, which compromised almost 87,000 “Fortinet” firewalls, and the “Arch Linux” AUR repository takeover, which turned over 400 packages into a channel for distributing malicious software. Alongside these, there was a successful law enforcement strike against the ‘infostealer’ ecosystem, DI toolkit vulnerabilities and France’s ultimatum to classical cryptography.
The most notable discovery of the month was made by SOCRadar researchers, who gained access to an active campaign called ‘FortiBleed’ through an insecurely open attacker server. It contains 86,644 (identified in over 194 countries) Fortinet firewall and VPN device logins, from banks and telecommunications operators to hospitals, universities and government agencies.
The most interesting thing is that this is not a zero-day attack. The campaign, which has been active since at least February, relies on two interdependent stages. The first stage involves credential reuse: passwords obtained from previous Fortinet leaks and infostealer logs are automatically and continuously checked against open devices. The second stage is passive collection: the compromised device is converted into a listening post that monitors the VPN traffic passing through it and collects new credentials, which are sent back to the scanner.
Analysis revealed an unpleasant truth: a large proportion of stolen logins consisted of shared administrator and factory-default “Fortinet” system accounts – many organisations never changed them, and the passwords remained unchanged even after previous leaks. SOCRadar attributed the campaign to the “Lynx/INC” ransomware group, and the assessment is clear: organisations that appear on the list should consider their perimeter already compromised.
The second major story hit the developers’ community. From 11 June, attackers took over more than 400 abandoned packages in the community-based ‘Arch User Repository’ (AUR) repository – such packages have no active maintainers, so anyone can ‘adopt’ them. To avoid arousing suspicion, they forged the ‘git’ history, imitating the work of a long-term maintainer, and inserted malicious code into the package creation scripts. The result: each computer that compiles such a package unnoticeably installs the ‘infostealer’. The official “Arch Linux” repository was not affected – the attackers exploited not a software vulnerability, but the AUR trust model itself.
The Rust-written code targeted the creators’ assets specifically: browser cookies and session tokens, GitHub, npm and SSH keys, Docker and OpenAI access data. When run with root privileges, it would install the eBPF rootkit, hiding its processes from standard tools – therefore, simply deleting the package is not enough; it is recommended that the infected system be re-installed from a reliable source. The campaign was named ‘Atomic Arch’ by the Sonatype researchers.
Check passwords and enable MFA: review all service and server logins, remove weak and repeated passwords, rename or disable factory accounts. Two-factor authentication is mandatory wherever possible, and management interfaces should not be publicly accessible. ‘FortiBleed’ showed that attackers often only need old, unmodified login details.
Control plug-ins and add-ons: Set clear rules for the centralised monitoring, inspection and approval of employees’ software add-ons and browser extensions.
Limit DI tool privileges: DI assistants, who have access to account management or other sensitive functions, themselves become a target for social engineering. Give them only the minimum necessary permissions and require additional identity verification before sensitive actions.
Start preparing for the quantum era: France has set a specific deadline, and other countries will most likely follow its example. It is worth inventorying where and what cryptography is used and planning the transition to quantum-resistant solutions now. The phrase ‘harvest now, decrypt later’ reminds us that data encrypted today may not necessarily be secure tomorrow.
This entry is published as part of the SOCshare project (No. 101145843), which we are running together with Vilnius City Municipality. It is partly funded by the European Union. The views and opinions expressed are those of the authors alone and do not necessarily reflect those of the European Union or the European Cyber Security Centre of Excellence. Neither the European Union nor the European Cyber Security Centre of Excellence can be held responsible for them.