{"id":922,"date":"2026-01-29T16:04:38","date_gmt":"2026-01-29T16:04:38","guid":{"rendered":"https:\/\/blog.ibvl.in\/index.php\/2026\/01\/29\/supply-chain-attack-on-escan-antivirus-detecting-and-remediating-malicious-updates\/"},"modified":"2026-01-29T16:04:38","modified_gmt":"2026-01-29T16:04:38","slug":"supply-chain-attack-on-escan-antivirus-detecting-and-remediating-malicious-updates","status":"publish","type":"post","link":"https:\/\/blog.ibvl.in\/index.php\/2026\/01\/29\/supply-chain-attack-on-escan-antivirus-detecting-and-remediating-malicious-updates\/","title":{"rendered":"Supply chain attack on eScan antivirus: detecting and remediating malicious updates"},"content":{"rendered":"
\n

\"\"<\/p>\n

On January 20, a supply chain attack has occurred, with the infected software being the eScan antivirus developed by an Indian company MicroWorld Technologies. The previously unknown malware was distributed through the eScan update server. The same day, our security solutions detected and prevented cyberattacks involving this malware. On January 21, having been informed by Morphisec<\/a>, the developers of eScan contained the security incident related to the attack.<\/p>\n

Malicious software used in the attack<\/h2>\n

Users of the eScan security product received a malicious Reload.exe file, which initiated a multi-stage infection chain. According to colleagues at Morphisec<\/a> who were the first to investigate the attack, Reload.exe prevented further antivirus product updates by modifying the HOSTS file, thereby blocking the ability of security solution developers to automatically fix the problem, which, among other things, led to the update service error.<\/p>\n

The malware also ensured its persistence in the system, communicated with control servers, and downloaded additional malicious payloads. Persistence was achieved by creating scheduled tasks; one example of such a malicious task is named CorelDefrag. Additionally, the consctlx.exe malicious file was written to the disk during the infection.<\/p>\n

How the attackers managed to pull off this attack<\/h2>\n

At the request of the BleepingComputer information portal, eScan developers explained<\/a> that the attackers managed to gain access to one of the regional update servers and deploy a malicious file, which was automatically delivered to customers. They emphasize that this is not a vulnerability \u2014 the incident is classified as unauthorized access to infrastructure. The malicious file was distributed with a fake invalid digital signature.<\/p>\n

According to the developers, the infrastructure affected by the incident was quickly isolated, and all access credentials were reset.<\/p>\n

How to stay safe?<\/h2>\n

To detect infection, it is recommended to review scheduled tasks for traces of malware, check the %WinDir%System32driversetchosts<\/code> file for blocked eScan domains, and review the eScan update logs for January 20.<\/p>\n

The developers of eScan have created a utility for their users that removes the malware, rolls back the modifications it has made, and restores the normal functionality of the antivirus. The utility is sent to customers upon request to technical support<\/a>.<\/p>\n

Users of the solution are also advised to block known malware control server addresses.<\/p>\n

Kaspersky\u2019s security solutions, such as Kaspersky Next<\/a>, successfully detect all malware used by attackers with its Behavior Detection component<\/a>.<\/p>\n

Indicators of compromise<\/h2>\n

Several malicious domain names and links were listed<\/a> in the Morphisec blog:<\/p>\n