12:17 PM

Bank Attackers Restart Operation Ababil DDoS Disruptions

Some customers report difficulty accessing banking sites, but officials said DDoS defenses and service provider blocks may be partly to blame.

The hacktivist Muslim bank website takedown crew is back.

The Izz ad-Din al-Qassam Cyber Fighters Tuesday announced via Pastebin that they would resume their Operation Ababil distributed denial of service (DDoS) attacks this week against U.S. financial institutions.

"During ... Operation Ababil Phase 3, like previous phases, a number of american banks will be hit by denial of service attacks three days a week, on Tuesday, Wednesday and Thursday during working hours," read the group's latest statement.

The al-Qassam Cyber Fighters last week issued an "Al-Qassam ultimatum", warning that unless all copies of the "Innocence of Muslims" movie that mocks the founder of Islam are removed from the Internet, it would commence a third round of bank DDoS attacks. "To warn and to show our seriousness for this, an attack string was carried out against some U.S. banks on Monday February 25, 2013 such as Bank of America, PNC, CapitalOne, Zions bank, 5/3, Unionbank, Comerica, Citizenbank, Peoples, UFCU, Patelco, and others," it said.

[ Anonymous targets Wall Street. Read Anonymous Launches Operation Wall Street, Targets CEOs. ]

This week, the group appeared to carry through with those threats. According to the Site Down website, beginning Tuesday, customers of Bank of America, Capital One, Citibank, PNC Bank, Union Bank and Wells Fargo began reporting an increased number of website disruptions.

One commenter on Site Down posted Tuesday morning, "Can not access Web site will not load...however...I CAN connect and log in using my iPhone. Strange." Another post read: "Site STILL down. Can we get a response??? am ready to take my banking elsewhere; this is getting ridiculous." Similar bursts of customer frustration were likewise directed at the other supposedly disrupted websites.

But have the banks' sites really been disrupted? BoA spokesman Mark T. Pipitone suggested otherwise. "At this point, we've had no issues on our end," he said via email.

Another bank official, speaking on background by phone, said that while many financial services websites are being targeted with DDoS attacks, people's inability to reach the websites is likely a side effect of the DDoS attack-scrubbing services and technology that firms now have in place, as well as service providers' own defenses. In other words, when a person can't access a banking site, it may be because their network, IP address or machine is being blocked by DDoS mitigation tools.

Furthermore, with a bank such as BoA alone counting 57 million customers, it can be difficult to tell whether the number of people who haven't been able to access a particular website on a given day has altered in a statistically significant way. Looking at BoA, over the past month the Site Down website received about 13 reports per day that the site couldn't be accessed. That number increased to an average of 18 per day this week, and 52 in the past 24 hours.

Of course, the combination of DDoS attacks and DDoS defenses does seem to be keeping some customers from accessing banking websites, even though the actual sites may still be up. That speaks to the scale of the website attacks -- and thus defenses in place against them. The attacks combine multiple attack techniques with massive scale, which has included maintaining sustained packet floods peaking at 70 Gbps and 30 million packets per second.

Attend Interop Las Vegas May 6-10 and learn the emerging trends in information risk management and security. Use Priority Code MPIWK by March 22 to save an additional $200 off the early bird discount on All Access and Conference Passes. Join us in Las Vegas for access to 125+ workshops and conference classes, 300+ exhibiting companies, and the latest technology. Register today!

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-12
vpxd in VMware vCenter Server 5.0 before u3e, 5.1 before u3, and 5.5 before u2 allows remote attackers to cause a denial of service via a long heartbeat message.

Published: 2015-10-12
The JMX RMI service in VMware vCenter Server 5.0 before u3e, 5.1 before u3b, 5.5 before u3, and 6.0 before u1 does not restrict registration of MBeans, which allows remote attackers to execute arbitrary code via the RMI protocol.

Published: 2015-10-12
Cisco Unified Computing System (UCS) B Blade Server Software 2.2.x before 2.2.6 allows local users to cause a denial of service (host OS or BMC hang) by sending crafted packets over the Inter-IC (I2C) bus, aka Bug ID CSCuq77241.

Published: 2015-10-12
The process-management implementation in Cisco TelePresence Video Communication Server (VCS) Expressway X8.5.2 allows local users to gain privileges by terminating a supervised process and then triggering the restart of a process by the root account, aka Bug ID CSCuv12272.

Published: 2015-10-12
HP 3PAR Service Processor SP 4.2.0.GA-29 (GA) SPOCC, SP 4.3.0.GA-17 (GA) SPOCC, and SP 4.3.0-GA-24 (MU1) SPOCC allows remote authenticated users to obtain sensitive information via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.