Does Internap try to cover up all the effects of a ransomware attack?

Does Internap try to cover up all the effects of a ransomware attack?

Cloud and data giant Internap (INAP) suffered a ransomware attack that caused its email, database and website services to be disrupted.

Despite little information online, the attack took place between 2:11 am CDT and 5:41 am CDT on September 28, before being discovered by a support technician at 8:00 am CDT.

But interestingly, the ransomware attack report was later removed from INAP's Operational Transparency Incident Report page (opens in a new tab).

Secret ransomware attack

Using the Internet archiving tool Wayback Machine, the previously reported incident on the INAP page indicated that the company's Incident Reporting Team was able to determine the root cause and the attack vector used.

Despite resolving the incident, INAP was unable to recover its clients' services due to the attack, and as a result, the company will no longer provide a multi-tenant website, database, web hosting (opens in a new tab), and web hosting. email (opens in a new tab) services, according to the report (opens in a new tab).

This means that customers who did not have third-party backup software (opens in a new tab) lost their services.

"We will terminate these multi-tenant hosting services and remove the charges from your account effective immediately. The multi-tenant "GuestDNS" service has not been affected and you can continue to make DNS changes (opens in a new tab) at through the control panel”, said the INAP.

"Our recommended way forward is to recreate all affected services on a full server and download their data from their local copies, if available."

Currently, the most recent incident reported on INAP's Operational Transparency page is the replacement of a faulty top rack switch in its Chicago data center, which affected its customers' systems in those cabinets, resulting in a loss of public network connectivity of 30 minutes.

LaComparacion Pro contacted INAP for more information about the incident, but the company has not yet responded.