1
Published signals
currently linked to this company
Company intelligence
escan.com
This company page brings together public reporting currently associated with Escan. It reflects signals published by Shadow Tier and should not be read as a complete incident history.
Company links
1
currently linked to this company
0
recent published signals
0
recent published signals
0
confidence classifications
July 22, 2026
most recent published signal
Company signals
eScan confirms update server breached to push malicious update MicroWorld Technologies, the maker of the eScan antivirus product, has confirmed that one of its update servers was breached and used to distribute an unauthorized update later analyzed as malicious to a small subset of customers earlier this month. The file was delivered to customers who downloaded updates from the regional update cluster during a two-hour window on January 20, 2026. eScan says the affected infrastructure has since been isolated and rebuilt, authentication credentials have been rotated, and remediation has been made available to impacted customers. Security firm Morphisec separately published a technical report analyzing malicious activity observed on customer endpoints, which it associates with updates delivered from eScan's update infrastructure during the same timeframe. Morphisec states that it detected malicious activity on January 20, 2026, and later contacted eScan. MicroWorld Technologies told BleepingComputer it disputes Morphisec's claims that it was the first to discover or report the incident. According to eScan, the company detected the issue internally on January 20 through monitoring and customer reports, isolated the affected infrastructure within hours, and issued a security advisory on January 21. eScan says Morphisec contacted the company later, after publishing public claims about the incident. eScan also disputes claims that affected customers were unaware of the issue, stating that it conducted proactive notifications and direct outreach to impacted customers while remediation was being finalized. In its advisory, eScan classified the incident as an update infrastructure access incident, stating that unauthorized access to a regional update server configuration allowed an unauthorized file to be placed in the update distribution path. "Unauthorized access to one of our regional update server configurations resulted in an incorrect file (patch configuration binary/corrupt update) being placed in the update distribution path," reads an advisory shared with BleepingComputer by MicroWorld Technologies. "This file was distributed to customers downloading updates from the affected server cluster during a limited timeframe on January 20, 2026." The company emphasized that the incident did not involve a vulnerability in the eScan product itself. eScan stressed that only those whose software was updated from the specific regional cluster were impacted, while all other customers remained unaffected. However, eScan says that those who installed the malicious update may have seen this behavior on their systems: Modified system hosts file preventing connection to eScan update servers eScan update configuration file modifications Inability to receive new security definition updates Update unavailability popup on client machines BleepingComputer contacted eScan with further questions on when its systems were initially breached and will update the story if we receive a reply back. Morphisec's security bulletin says that the malicious update pushed down a modified version of an eScan update component, "Reload.exe". "Malicious updates were distributed through eScan's legitimate update infrastructure, resulting in the deployment of multi-stage malware to enterprise and consumer endpoints globally," reads Morphisec's bulletin. While the modified Reload.exe is signed with what appears to be eScan's code-signing certificate, both Windows and VirusTotal show the signature as invalid. According to Morphisec, the Reload.exe file [ VirusTotal ] was used to enable persistence, execute commands, modify the Windows HOSTS file to prevent remote updates, and connect to the C2 infrastructure to download further payloads. The researchers say the following command and control servers were observed:
FAQ
It combines a reviewed organization profile with all current published Shadow Tier signals explicitly linked to Escan.
No. A signal must contain a reliable company connection and meet the publication criteria; incidental or ambiguous mentions are excluded.
The page follows current published reporting. Counts change as new evidence is added, classifications are reviewed, or older signals leave the reporting window.