Regrettably, the initial report of 32 affected users were later reconfirmed to 17; 15 of the initial count had interacted with the attacker but not lost tokens as a result.