Federal appeals court raps bank over shoddy online security

The case marks another sign that banks are being taken to task for inadequate wire transfer systems
  • Jeremy Kirk (IDG News Service)
  • — 05 July, 2012 05:32

A U.S. construction company may stand a greater chance of recovering some of the US$345,000 it lost in fraudulent wire transfers that it blames on poor online banking practices of its bank.

Patco Construction Company, based in Sanford, Maine, sued Ocean Bank, now called People's United Bank, after fraudsters made six wire transfers using the Automated Clearing House (ACH) transfer system amounting to more than $588,000 in May 2009. About $243,000 was recovered.

In its suit, Patco alleged among other claims that Ocean Bank's online security was not commercially reasonable under Article 4A of the Uniform Commercial Code (UCC), a federal code governing contractual disputes that has been adopted into most U.S. states' laws.

The UCC does not allow claims such as negligence, fraud and breach of contract. The code makes it potentially costly for small businesses to sue financial institutions over cybercrime-related fraud. Even if a small business wins a lawsuit, under the code the financial damages are limited only to the money stolen plus interest.

In a significant twist, a three-judge federal appeals court panel found on Tuesday that Ocean Bank's online security measures were not "commercially reasonable," reversing a lower court ruling from May 2011.

It doesn't mean that Patco will be refunded. The appeals court said further hearings will be needed to determine what responsibilities Patco may have had to protect itself during online banking transactions. The court also advised that despite its ruling, Patco and Ocean Bank may want to try to settle the issue out of court.

But the latest ruling is a sign that small businesses are having greater success at shifting liability towards banks in online security meltdowns, including out-of-court settlements.

Patco maintains the fraudulent transfers were caused by the Zeus malware, which can capture authentication credentials enabling fraudsters to initiate their own illegitimate transfers.

In its decision, the appeals court cited a critical mistake made by Ocean Bank as ACH fraud had become more prevalent. In June 2008, Ocean Bank decided to initiate "challenge questions" for any transactions for its customers valued at more than $1.

Challenge questions are often used in authentication systems and require a user to enter additional information aside from a login or password, such as the name of the first street a person lived on or the model of their first car.

Since the answers to the challenge questions were displayed every time Patco made a transfer, this "increased the risk that such answers would be compromised by keyloggers or other malware that would capture that information for unauthorized uses," according to the ruling.

The court also found that Ocean Bank was not monitoring its transactions for fraud nor notifying customers before a suspicious transaction was allowed to proceed, both capabilities that it did possess with its security system.

Patco used the ACH system to process its weekly payroll in amounts never exceeding $37,000. The fraudulent transfers, however, were in much higher chunks: $56,594, $91,959, $99,068, $111,963, $113,647 and $115,620.26.

All of the transactions were "uncharacteristic in that they sent money to numerous individuals to whom Patco had never before sent funds, were for greater amounts than Patco's ordinary third-party transactions, were sent from computers that were not recognized by Ocean Bank's system, and originated from IP addresses that were not recognized as valid IP addresses of Patco," the ruling said.

Send news tips and comments to jeremy_kirk@idg.com

Comments are now closed.
CSO Corporate Partners
  • Webroot
  • Trend Micro
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

Cloud Security and Compliance Solutions

Manage and visualize the security and compliance of VMware, physical, and hybrid-cloud infrastructure from the RSA Archer eGRC Platform.

Security Awareness Tip

Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).


  1. Have an incident response plan.

  2. Pre-define your incident response team 

  3. Define your approach: watch and learn or contain and recover.

  4. Pre-distribute call cards.

  5. Forensic and incident response data capture.

  6. Get your users on-side.

  7. Know how to report crimes and engage law enforcement. 

  8. Practice makes perfect.

For the full breakdown on this article

Security ABC Guides

Warning: Tips for secure mobile holiday shopping

I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.