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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

B.3<br />

SEC v. Kelly, 2011 WL 44331161 (S.D.N.Y. Sept. 22, 2011).<br />

The SEC brought securities fraud charges against defendants alleging that they<br />

engineered transactions that allowed the corporation to improperly report over $1 billion in<br />

revenue from online advertising. After the Supreme Court issued its decision in Janus Capital<br />

Group, Inc. v. First Derivative Traders, --- U.S. ---, 131 S. Ct. 2296 (2011), certain defendants<br />

moved for judgment on the pleadings on the SEC’s claims brought pursuant to Section 10(b) of<br />

the Exchange Act and Section 17(a) of the Securities Act. The SEC conceded that Janus<br />

foreclosed a misstatement claim against certain defendants under subsection (b) of Rule 10b-5<br />

because neither defendant “made” a misleading statement. The same defendants also moved for<br />

judgment on the pleadings on the SEC’s claim brought pursuant to Section 17(a) of the<br />

Securities Act. The defendants argued that because a claim for misstatement liability under<br />

Section 17(a) is treated identically to a claim under Section 10(b), the SEC’s Section 17(a) claim<br />

must also be dismissed on the basis of Janus. The court concluded that although the language of<br />

subsection (2) of Section 17(a), which applies to misstatement liability, is not identical to that of<br />

subsection (b) of Rule 10b-5, because both provisions have “the same functional meaning” with<br />

respect to creating primary liability, Janus applies to Section 17(a)(2) claims as well as Section<br />

10(b) claims. The court stated that it would be inconsistent for Janus to require that a defendant<br />

have actually “made” the misleading statement to be liable under subsection (b) of Rule 10b-5<br />

but not under subsection (2) of Section 17(a).<br />

SEC v. Citigroup Global Markets Inc., 2011 WL 5903733 (S.D.N.Y. Nov. 28, 2011).<br />

The SEC filed a complaint against Citigroup alleging violations of Sections 17(a)(2) and<br />

(3) of the Securities Act over a collapsed $1 billion mortgage-bond fund. According to the<br />

complaint, during early 2007, Citigroup created a billion-dollar fund that sought to “dump” some<br />

toxic mortgage-backed securities on “misinformed investors.” Citigroup allegedly pitched the<br />

Fund’s assets to prospective investors as attractive investments rigorously selected by an<br />

independent investment adviser; however, in reality, Citigroup purposely selected a substantial<br />

amount of negatively performing assets for inclusion in the Fund and then took a short position<br />

in those assets, betting that their value would decline over time. Investors in the Fund lost more<br />

than $700 million, while Citigroup reaped net profits of approximately $160 million.<br />

The same day the complaint was filed, the SEC and Citigroup filed a proposed consent<br />

judgment. Both the SEC and Citigroup asserted that the proposed settlement was “fair,<br />

reasonable, and in the public interest,” and asked the court to approve the proposed settlement.<br />

In response, Judge Rakoff asked both parties to answer several questions concerning the<br />

proposed consent judgment. After receiving responses to the court’s questions and hearing<br />

argument, Judge Rakoff rejected the proposed $285 million settlement between the SEC and<br />

Citigroup and concluded that because the SEC’s standard, boilerplate “neither admit nor deny”<br />

settlement language failed to satisfy the required standard in evaluating such settlements, the<br />

proposed settlement would not be approved. Judge Rakoff concluded that the district court could<br />

B.3<br />

53

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

Saved successfully!

Ooh no, something went wrong!