All vulnerabilities
CRITICALPhishingexploited in the wild

PHISH-RSA-SECURID-2011

Phishing · Spear phishing · RSA SecurID (EMC)

Summary

In March 2011, attackers breached RSA Security (then part of EMC) with a spear-phishing email. Two small batches of messages subject-lined '2011 Recruitment Plan' were sent to low-profile employees with an Excel attachment; opening it triggered an Adobe Flash zero-day (CVE-2011-0609) that installed a Poison Ivy backdoor. From that single foothold the attackers escalated privileges, identified and stole privileged-user credentials, and exfiltrated data related to RSA's SecurID two-factor tokens. The stolen seed-related data was subsequently used in an attempted intrusion at defense contractor Lockheed Martin. RSA ultimately offered to replace SecurID tokens for affected customers, with remediation costs reported around $66 million. It is the canonical case of one opened attachment cascading into a supply-chain-grade compromise.

How to avoid it in your code

  • Patch or disable risky client-side runtimes (Flash, legacy Office macros) and detonate attachments in a sandbox.
  • Deploy EDR to catch RAT and backdoor behavior rather than relying on signature antivirus alone.
  • Segment and least-privilege seed and secret material so one phished workstation cannot reach it.
  • Hold high-value secrets (token seeds, signing keys) in an HSM with tight access logging.
  • Train all staff, not just executives; this attack deliberately targeted low-profile employees.

References

Related vulnerabilities

All Phishing →