Archive

ReliaQuest appears to have been targeted through social engineering rather than a technical exploit, and the incident became public through taunting by ShinyHunters. For defenders, that raises the priority of identity controls, employee verification procedures, and limits on what a single compromised user can expose.

ReliaQuest is pushing back on claims that it was compromised in the ShinyHunters incident. For defenders, the main issue is verification: whether the company was actually affected and whether any related exposure extends to customers, partners, or internal systems.

ReliaQuest says it was hit by ShinyHunters, but the company describes the impact as limited. For defenders, the key point is exposure to a known extortion and breach-focused threat actor, with the main obligations being incident containment, access review, and customer or partner notification if any data was touched.

Attackers are using impersonation of a security vendor’s staff to try to collect single sign-on credentials and MFA access. That raises the risk of account takeover for any organization that relies on those authentication controls and vendor trust relationships.

ReliaQuest says it was targeted in a data-theft attempt tied to the ShinyHunters breach, and the attempt did not succeed. For defenders, the immediate issue is exposure to follow-on targeting after a related intrusion, with attention on data access, account security, and whether other connected systems were touched.