Sberbank

Summary

Oschadbank experienced a DDoS attack that caused temporary slowdowns in accessing its online banking platform due to overloaded communication channels. The institution confirmed all systems remained secure and fully operational, with no compromise of customer data or critical banking services. Technical teams actively worked to mitigate the attack's effects and restore normal system performance, minimizing disruptions for users while maintaining standard protective measures throughout the incident.

Motives

Detailed motive labels are available to members.

TTPs

Detailed technique labels are available to members.

Description

On February 15, 2022, Oschadbank publicly disclosed it was experiencing a distributed denial-of-service (DDoS) attack targeting its digital infrastructure. The attack caused measurable operational disruption, specifically impacting customer access to the Oschad24/7 online banking platform. Technical monitoring revealed the DDoS generated abnormally high traffic volumes, overloading communication channels and resulting in significantly slower system response times for users attempting to authenticate or conduct transactions. The bank confirmed its core banking systems remained secure and fully operational throughout the incident, with no reported compromise of customer data or financial assets. Service degradation was confined to accessibility delays rather than systemic failures, indicating the bank's defensive measures partially mitigated the attack's impact.

Oschadbank's incident response team initiated mitigation protocols immediately upon detecting the anomalous network activity. Public communications emphasized ongoing efforts to restore normal service speeds while acknowledging temporary inconveniences to customers. The bank issued a formal apology for the disruption but did not disclose specific technical details about the attack's origin, duration, or the total volume of malicious traffic involved. No additional disruptions to branch operations, ATM networks, or internal banking processes were reported alongside the Oschad24/7 slowdown. The incident concluded with the restoration of standard access speeds, though the timeline for full resolution remained unspecified in available disclosures.

Sources

Sources available to members: 1 source.