A relatively new hacker group has claimed responsibility for a significant cyber attack on Nottingham-based transportation technology solutions provider, the Microlise Group, that disrupted daily operations at several of its clients.
In a data security incident notification filed with the London Stock Exchange on Oct. 31, Microlise said that it suffered a cyber attack that affected “large portion of the Company’s services” and “resulted in disruption to services which are currently inactive.”
The company launched an investigation and has appointed external cyber security experts to determine the nature and scope of the incident. Microlise also notified relevant regulators and law enforcement agencies, including the Information Commissioner’s Office.
In a separate update shared with the London Stock Exchange, Microlise said its investigation revealed that the cyber security incident did not compromise any data stored in its customer systems even though the incident had impacted their functioning.
Later, on November 6, the company informed the London Stock Exchange that the incident impacted limited employee data but did not state the number of employees whose data was accessed.
Recently, a novel ransomware group going by the name SafePay claimed responsibility for the cyber attack on the company and listed it as a victim on its data leak site.
The group claims to be in possession of 1.2 terabytes of data stolen from the company and has set a deadline of November 22 for Microlise to meet its ransom demands, failing which the hacker group has threatened to leak the stolen data.
Microlise is yet to comment on the claims of the threat actor. Also, it did not share details on whether it received a ransom demand or how the hackers infiltrated its systems.
The company has, however, clarified that customers’ financial information, including banking data, passwords, and PIN codes, were not accessed by the threat actor.
The company has, however, clarified that customers’ financial information, including banking data, passwords, and PIN codes, were not accessed by the threat actor.
