Metascan Confirms Limited Data Breach After Two-Minute Telegram Bot Compromise

Metascan has publicly acknowledged a data breach involving internal materials obtained through a compromised Telegram bot token. The attacker gained access to a corporate Telegram chat for approximately two minutes on September 5 and exported a small set of documents before being removed. The incident stemmed from an overlooked bot token on test virtual machines after an employee departure. Among the leaked items were two pilot project reports from July 2026 that mentioned major Russian organizations including Transneft, Selectel, Lenta, Sberbank, and Rostelecom. Metascan attributed the leak to a former employee now working with a competitor and rejected claims of deliberately hidden vulnerabilities. The company has accepted full responsibility, outlined corrective measures, and launched a bug bounty program.

AntiMalwareTranslated from Russian

Read at source

Metascan, a company providing vulnerability scanning and information security services, has confirmed an internal data leak and released the findings of its investigation. According to the company, an attacker remained in a corporate Telegram chat for roughly two minutes and managed to export only a limited set of documents.

The incident occurred in the early hours of September 5. The attacker used a compromised administrative token belonging to a Telegram bot and added a fake account disguised as an HR employee. Export of the chat began at 02:02 and was interrupted at 02:04 when the account was removed. The bot itself had no access to client chats but held administrator rights in the internal corporate chat.

The company stated that the attacker obtained a small volume of data, including two pilot project reports dated July 2026. Earlier, the threat actors published internal documents and screenshots referencing Transneft, Selectel, Lenta, Sberbank, Rostelecom and other large organizations. They also alleged that Metascan had concealed client vulnerabilities to sell remediation services later. Metascan rejected these claims and linked the publication to a former employee now cooperating with a competitor.

The root cause was identified as an internal error: while primary tokens were revoked upon the employee’s departure, a token remained active on test virtual machines. Metascan has fully accepted responsibility, announced plans to strengthen technical controls, and stated its intention to pursue legal assessment of the actions involved. The company has also launched a vulnerability disclosure program, accepting reports at bb@metascan.ru prior to publication on specialized platforms.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Data Breaches & Leaks

Yandex Restores Access to 96% of Yandex Disk Data After Data Center Attacks
k0t Operators Breach Corporate Firewalls and VPNs Exposing Over 70,000 Credentials
OpenCode Reports Possible Exposure of Third-Party API Keys After Legacy System Breach