The SSV team has published an analysis of two slashing incidents, which were related to validator key management rather than protocol issues.

BlockBeats News, September 11: The SSV team released a detailed post-mortem analysis of two recent slashing incidents. The monitoring system first flagged a slashing event on Wednesday at 11:51 UTC. Approximately 90 minutes later, a second, larger-scale slashing event affected 39 validators. Investigations revealed that both events originated from external factors to the SSV protocol, specifically related to validator key management.

In the two incidents, the larger-scale event was linked to long-term staking service provider Ankr. Ankr acknowledged that a validation key was mistakenly active in two different infrastructures due to operational maintenance misconfiguration, leading to the slashing. The company promptly shut down the affected operator and collaborated with SSV Labs to confirm the root cause. The smaller-scale event involved validators migrated from the hosting service provider Allnodes, and is currently under investigation, with suspicions that auxiliary validator settings also played a role.

Alon Muroch, CEO of SSV Labs, stated that the validator slashing events did not compromise the SSV protocol, and operators or stakeholders do not need to take any action. Upon reviewing the logs of the two events, no evidence was found to suggest double-signing or malfunctions on the SSV side.