04.01.2014 Views

Broker-Dealer Litigation - Greenberg Traurig LLP

Broker-Dealer Litigation - Greenberg Traurig LLP

Broker-Dealer Litigation - Greenberg Traurig LLP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

held that the statute of limitations begins to run at the point which plaintiff was on “inquiry<br />

notice” of the fraud. However, the court recognized the new inquiry notice standard, as<br />

recognized in the U.S. Supreme Court case Merck & Co. v. Reynolds, 130 S.Ct. 1784 (2010),<br />

which focused on when a reasonable investor would have actually uncovered the facts<br />

constituting the fraud. The court found plaintiff’s complaint was not time barred because, based<br />

on the allegations in the complaint, nothing indicated the plaintiff should have discovered the<br />

fraud.<br />

In re STEC Inc. Securities <strong>Litigation</strong>, 2011 WL 2669217 (C.D. Cal. June 17, 2011).<br />

C.1.f<br />

Plaintiffs brought a class action suit against defendants alleging defendants made false<br />

statements and omissions that inflated the company’s stock price and ultimately caused the price<br />

to collapse when the truth was disclosed. In particular, plaintiffs alleged that defendants falsely<br />

represented its business prospects, including falsely stating that a particular purchase contract by<br />

defendants’ largest customer would be continually renewed, when in fact it would not.<br />

Defendants moved to dismiss the claim for failure to state a claim and that Plaintiffs had not<br />

sufficiently alleged the existence of a false statement in the registration statement or prospectus.<br />

Defendants also asserted the affirmative defense of the safe harbor provision of the Private<br />

Securities <strong>Litigation</strong> Reform Act of 1995 (“PSLRA”), and the bespeaks caution doctrine. The<br />

court found that the bespeaks caution doctrine provides a mechanism by which a court can rule<br />

as a matter of law that defendants’ forward-looking representations contained enough cautionary<br />

language or risk disclosure to protect a defendant against claims of securities fraud. However,<br />

the court held that the statements made by defendants were not meaningfully cautionary because<br />

they did not relate directly to the forward-looking statements at issue. Specifically, the<br />

cautionary statements were not of sufficient similar significance to the recurring nature of the<br />

purchase contract to indicate it was a “one-off” contract. Accordingly, the court denied<br />

defendants’ motion to dismiss.<br />

In re Verifone Holdings Inc. Securities <strong>Litigation</strong>, 2011 WL 1045120 (N.D. Cal. Mar. 22, 2011).<br />

C.1.f<br />

This case represents the consolidation of nine securities fraud class actions filed against<br />

defendants, including officers of defendant corporation, relating to the corporation’s public<br />

announcement that it had to restate its quarterly financial statements for at least the previous<br />

three quarters to correct errors that overstated previously reported profits. In particular, plaintiffs<br />

alleged that several of the corporate officers committed insider trading in violation of the<br />

Securities Exchange Act of 1934 by trading company stock on this information prior to the<br />

public announcement. On defendants’ motion to dismiss, several of the defendants claimed that<br />

Rule 10b5-1 acted as an affirmative defense to the insider trading claim. Rule 10b5-1 permits an<br />

insider with inside information to trade in stock so long as the trades were pursuant to a contract,<br />

instructions given to another or a written plan that did not permit the person to exercise any<br />

influence over the purchase or sale of stock after learning the inside information. Accordingly,<br />

the court found that so long as defendants executed the purchase or sale of defendants’ stock<br />

91

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!