(UPDATED December, 2011) Finally, a little of TD Ameritrade’s money is going to a few of the class members it ripped off.  It’s taken 6 years to get here!  Though TD Ameritrade refuses to pass a security audit and covered up the breach, the government (in the form of the SEC and the federal judiciary), and the Financial Industry’s self-Regulatory-organization Authority (FINRA, nee NASD) have let it off with a ‘slap on the wrist’ that will have no material impact on the company. I guesstimate the  ‘slap on the wrist’ was over $40 million:$6.5 million for the settlement, plus the cost of my attorneys, their attorneys, printing, stuffing and mailing over 12 million letters, litigation costs (flying dozens of attorneys to San Francisco), increased insurance costs, loss of business, etc.   Criminals had gained ongoing access to TD Ameritrade’s customer database back in October, 2005.   This database contains 6.3 million+ customers’ names, addresses, mailing addresses, email addresses, trading histories, account numbers, account balances, dates of birth – oh, and social security numbers too.  AMTD knew of, covered up, and failed to fix the problem for TWO YEARS. How do I know this?

Notes for new readers:

  • If you’re new here or found this useful, or just want to offer your support, please add a comment. I will keep the comment private, if you prefer.
  • This article is sticky, which means it always appears at the top. Other articles appear below this one, newest first.
  • Like on many blogs, only part of each article on the site appears on the main page. (The whole article becomes viewable if you click the title.) The bulk of the article becomes viewable if you click the “(more…)” tag after reading to the end of the teaser text. Like this:


These coordinates mean ‘unknown’ and are equivalent to 123 Anywhere St, AnyCity ST 12345, USA.  (Though they happen to specify an actual place, it’s in the middle of a lake.)

This google search : https://www.google.com/search?q=site:ipaddress.com+37.7510 shows the Latitude coordinate appears around 4 hundred thousand times on just one site.  (About 398,000 results.)

And the full Latitude – Longitude also appears around 400,000 times on just that one site per https://www.google.com/search?q=site:ipaddress.com+37.7510+97.8220!

(Kinda OT for this blog, but not entirely.). Purpose: save others time. And maybe they’ll stay and learn about the amazing bank-security/court scandal documented here

The datalossdb.org folks finally approved my reply to their reporting on my case, which has been in their moderation queue for 2 and a half years!  (And had been posted here at : https://caringaboutsecurity.wordpress.com/2016/05/06/looking-back/ .)  Apparently, their WordPress installation wasn’t working, and their project is in hibernation mode.


The TD Ameritrade incident of 2007 hasn’t quite been resolved — yet. While the breach may have been contained, the litigation is still ongoing. A class action suit field in California in May of 2007 has reached a preliminary settlement, but the settlement is contested by the individual who filed the class in the first place and has been through some extremely interesting twists and turns.

The case was filed in May of 2007, with a complaint that claimed that TD Ameritrade was essentially selling email addresses of clients to spammers, in violation of TD Ameritrade’s privacy policies and various laws.

A motion for a preliminary injunction kicked things into gear in July 2007, which alleged that the spam was still ongoing, and demanded that TD Ameritrade take steps to protect members of the class (TD Ameritrade customers). The fact that the incident was still ongoing at the time of…

View original post 2,196 more words

This is a response to DataLossDB blog post Legal Sub-Project – Elvey v. TD Ameritrade by jkouns on June 14, 2009

You ask some tough questions, and I have answers!  This is Elvey.  I filed the case. I was not aware of this post ’till now and want to belatedly direct any potential readers to some information that should further inform, as well as correct some inaccuracies.

I greatly appreciate your coverage of the case and particularly your highlighting and clear explanation of some of the key details that others have glossed over, like detailing the lack of substantial improvements in the new settlement, the far-fetched reasons for sealing the deposition (even from my own eyes!), and especially your picking apart the ridiculousness of the whole ‘presumption that since no evidence of “organized misuse” exists, Social Security numbers had not been compromised.’ concept.

I want to emphasize that my initial case filing alleged a “classic pump-and-dump scheme”, with a definition, references and strong evidence that the scheme benefited TD Ameritrade, not mere garden variety spamming.

What brought the compromise of Social Security numbers to light was the injunction I filed that forced TD Ameritrade to disclose it, not the suit Zigler filed.  (By the way, Zigler was someone I found. Zigler was a victim of the breach and my attorneys and I reached out to him and he joined my case very early on.  (The initial case caption is “[Me] and GADGETWIZ, INC., an Arizona corporation [owned by Brad Zigler], on their own behalf and on behalf of all others similarly situated,Plaintiffs v. TD AMERITRADE…”)) Over a year later, the firm of Scott Kamber, the crooked attorney who flew to San Francisco to arrive at my home unannounced to back the threats he had made on the phone and via email after I balked at the shitty settlement terms he negotiated, filed the Brad Zigler v. TD Ameritrade case. Some of the threats are described and quoted in a court filing and this blog post; links to the former, document Dkt 175.  I stand by the accuracy of the quotes in that filing. Do they not convince you that Kamber’s claim that  “Never was Mr. Elvey threatened or even pressured in any manner.” is a lie?  I think the Trial Lawyers closed ranks to protect one of their own, instead of rooting out the documented threat or the corruption that motivated it. Despite strong pressure and direct legal advice to keep quiet about the threats, I refuse to back down.

You claim /ask: “Why did Elvey approve the settlement in the first place?”  But as I noted on my blog in the post linked to above, “KamberEdelson filed document Dkt 53-2 with the court (the first proposed settlement), to my case’s docket, which shows my signature on a signature page I signed (i.e. it is my signature) but it’s been placed into a document I did not sign.”

What I haven’t thought to made public ’till now is some further evidence to back that up:

On Thursday, May 22, 2008, I emailed the court of Judge Vaughn Walker directly:

“I’m just following up on an urgent message I left with VRW’s
docket clerk and discussion with his court deputy.

Please do not accept any settlement agreement my attorneys file
that purports to contain my signature or assent to a settlement
without verifying that signature or assent with me directly.  You
should expect any documents that purport to have my signature to
be digitally signed (e.g. like this email – with a with an S/MIME
or PGP/GPG key).

I’d be happy to explain further in court; I’d explain here but I
have been told that I shouldn’t; it might be inappropriate ex
parte communication.

-Matthew Elvey, Plaintiff.”

Once presented with the surprising, horrible settlement draft  and threatened, I had begun figuring out what to do, begun searching for alternate counsel to represent the class and anticipated the filing that was made days later.  I’d been assured TD Ameritrade had agreed that the settlement would include passage of real (internal) security audits, no release of liability for ID theft, and a substantial breach-fighting non-profit (like the OSF) donation component, but it didn’t!

I hope that answers your question: “Why did Elvey approve the settlement in the first place?”  Clear?

You ask, “Is TD Ameritrade not already required by industry standards like PCI, or better yet, its own internal security policies to do so?” I answered that in this old blog post.

I’m generally very skeptical and a Yale-educated scientist – not one to believe conspiracy theories.  I see conclusive evidence of corruption by key parties this case. That, plus strong but not conclusive evidence has me convinced that there’s also corruption behind other odd decisions in the case that you mention, like support for and approval of the slightly improved settlement version that as you say, “substantively didn’t really alter much”.

Judge Walker repeatedly asked the former class counsel to place a value on the benefits the rejected settlement offered to the class. I think it’s doable, and no one has truly done so, so I’m going to give it a shot.

  • The audit component does not require TD Ameritrade to fix the problems found, and mainly benefits the firm, not its clients, so I give it a value of $50.  Weekly penetration testing can be ordered for about $100/per YEAR, so this is generous. I discussed this in more detail in my CMC statement (see page 10 of that document) and in a forthcoming (currently private) blog post dedicated to this component.
  • Regarding the software offered in the rejected settlement: TD Ameritrade defied the judge’s order; they never plainly stated how much they had or would pay for the software.  Though I was given an approximation, I can’t disclose it, and have little faith in the source or the number (and no, it’s not from a whistleblower).  I feel the software component should be valued based upon actual redemption rates, as tracked by proof of payments received for the software by the software firms from TD Ameritrade after the final settlement date. For each class member who downloads (and if activation is required, activates) the software, the value should be $5 (This is five times the amount the firm has implicitly represented as the cost.) If the Trend Micro or other software comes with the standard 3-year, 3-computer license, then its valuation should be trebled.  Postscript: it seems I was right to not trust the source for the approximation; I was told TD Ameritrade had already paid or committed to pay a certain amount the software.  If that was true, they wouldn’t have removed it from the settlement agreement, as it was a sunk cost, even if its value was being discounted by the court, it certainly still had some value. 

KamberEdelson/KamberLaw/Edelson McGuire law firm/attorney compensation, if any should be based not upon the rates they proffered the court, but rather upon the hourly rates at which the firm agreed to represent the class, as recorded in the contract signed May 14, 2007, of $500 (Scott Kamber and Alan Himmelfarb), and $335 (Ethan Preston and Dana Rubin), and an appropriate multiplier, and on the value of the settlement, and factoring the quality of the representation – which led to another firm, Kreindler and Kreindler stepping in as lead plaintiff’s counsel.

The SEC has a pathetic new regulation, its first on cybersecurity.  It’s another cog in a system designed to provide the appearance of Justice without actually meting it out to the very powerful or wealthy.  The SEC refused to act on warnings about the TD Ameritrade breach, the Madoff scam, and is poised to … continue to do more of the same…

How do I feel?

I feel like the justice system has let me down, like the Wall Street protesters who, e.g. want to see the executives of my former employer who lied to congress at least get arrested.

TD Ameritrade (TDA) has refused to pass a security audit, and the attorneys supposedly representing the class are OK with that. If TDA had secured their customer data properly, they would, most certainly, be eager to show their customers and target market.

My friends and I are angry that TDA’s security is still Swiss cheese. Earlier this year, they accidentally admitted that they didn’t even have an IDS or IPS system in place! I hear they still don’t encrypt customer data and still grant staff far more customer data access than is needed to do their jobs. They’re in violation of Massachusetts law. They’re literally making millions serving customers over the Internet that they wouldn’t make without the Internet, but not taking the small steps necessary to protect those customers. They spent millions on attorneys (at one judge-managed mediation session, there were ~30 attorneys present.) Instead of covering up their mistakes, they should be doing the right thing.

They profit off the Internet, but won’t invest in it! Their databases are an open book to gangs and even determined high-school students. They should be hiring and training their staff and deploying resources so that they can pass a security audit. They’ll get hacked again. And when they do, they’ll be back in court. And this warning, which I delivered in court, will haunt them.

The Armstrong court cherry picked which objections in my final filing to address and which to ignore.  The court demonstrated that it doesn’t even understand the 9th District’s own General Order (regarding PDFs) because it’s too technical!  (Even though it’s quite simple.)  There’s no way it understood all the key technical security issues in this case.

There’s been a news blackout with respect to the fact that TD Ameritrade actively covered up the security breach, as the whistleblower-sourced information I’ve published here details.

I’m glad that TD Ameritrade has at least received some bad press for its disgraceful behavior, and that those who filed claims are expected to receive significant compensation.  I’m glad that the bulk of the class is at least somewhat aware of the breach.  Unfortunately, the insignificant cost of this settlement sends the message that executives who underfund the Information Security department and direct the cover-up of a security breach breach are making the right choices, as far as the financial interests of shareholders go.  TDA would need to spend more than it spent settling this case to shore up its security enough to pass a proper audit.

I’m sick and tired of having essentially no choice but to intentionally expose my computer to attack and root compromise by any resourceful and motivated adversary.  It’s time to do more about it.  COMING SOON:  elvey.com/insecure

Should I sue the makers of this film for copyright infringement?

I’m joking, of course, in case that wasn’t obvious.  However, this film does a damn good job portraying what the InfoSec department at TD Ameritrade was (and, unfortunately, still is) like.  Counsel recently informed me, probably not realizing the foolishness it exposed, that TD Ameritrade DID NOT HAVE AN INTRUSION DETECTION SYSTEM(IDS) (or an Intrusion Protection System (IPS)) in place!

Watch it. (just Episode 1! It’s just 4 minutes.  Definitely skip Episode 2. Episode 3 is weak too.)

And no, I’m not endorsing AppSec or DBPROTECT.

Note the underlined bits.  Note the choice of words used.  Spam, instead of Security Breach.  “Other personal information”, instead of “including Social Security Numbers, Account Balances, Home Addresses and Phone Numbers” or better yet, the – still undisclosed – complete actual list of the data fields in the compromised database.
I’ve been following TD Ameritrads’s SEC Filings – 10-Q’s, etc.
In one 10-Q, I find this note about the case; similar notes are in other 10-Q’s:
Spam Litigation – A purported class action, captioned Elvey v. TD Ameritrade, Inc., was filed on May 31, 2007 in the United States District Court for the Northern District of California. The complaint alleges that there was a breach in TDA Inc.’s systems, which allowed access to e-mail addresses and other personal information of account holders, and that as a result account holders received unsolicited e-mail from spammers promoting certain stocks and have been subjected to an increased risk of identity theft. The complaint requests unspecified damages and injunctive and other equitable relief. A second lawsuit, captioned Zigler v. TD Ameritrade, Inc., was filed on September 26, 2007, in the same jurisdiction on behalf of a purported nationwide class of account holders. The factual allegations of the complaint and the relief sought are substantially the same as those in the first lawsuit. The cases were consolidated under the caption In re TD Ameritrade Accountholders Litigation. The Company hired an independent consultant to investigate whether identity theft occurred as a result of the breach. The consultant has conducted four investigations since August 2007 and reported that it found no evidence of identity theft. The parties entered into an agreement to settle the lawsuits on a class basis subject to court approval. On May 1, 2009, the Court granted preliminary approval of the proposed settlement, which had been revised, and set a hearing on final approval for September 10, 2009. Some class members have filed objections and opt-outs. The settlement is not expected to have a material effect on the Company’s financial condition, results of operations or cash flows.

I will make them talk. A, B, C, and D (not their real names) are all current or former members of TD Ameritrade’s InfoSec group.

Over a month ago, I filed and served a legal subpoena for their emails about the breach.  I also subpoenaed all the reports by internal staff and involved outside firms, which include ID Analytics, Mandiant and Protiviti, regarding the breach, which I understand will cover at least five security audits related to investigating the breach.

But TD Ameritrade has refused to honor the subpoena – AT ALL.

The other things I subpoenaed were:

C) A copy of the circa September 18, 2007 deposition of the former TD Ameritrade CSO (Chief Security Officer) regarding this breach.

D) TD Ameritrade stated on September 15, 2008, “We know specifically when the breaches began.” We request a copy of a document disclosing that date.

E) A copy of each Letter to the Audit Committee and Letter to the Audit Committee Chairman from the company’s auditors from 2005 to 2010, inclusive. Discusson of deficiencies that could have no impact on customers could be redacted.

I called the Claims Administrator yesterday, at 1-888-749-8173. The firm is well known in its field: Rosenthal & Co, which part of Computershare.  What a fiasco!

WarningDO NOT USE the information (more…)