How I Lost My $50,000 Twitter Username
A story of how PayPal and GoDaddy allowed the attack and caused me to lose my $50,000 Twitter username. — My $50,000 Twitter Username Was Stolen Thanks to PayPal and GoDaddy — I had a rare Twitter username, @N. Yep, just one letter.
Context & Ripple Effects
The loss of @N links PayPal, GoDaddy and Twitter in a single account-recovery chain: a failure at services used to establish identity can transfer control of a scarce social-media identifier. PayPal had already drawn scrutiny in 2010 after a user's account displayed a negative $900,000 balance, giving the incident a broader trust-and-account-controls backdrop.
The account's stated $50,000 value makes the case more than a customer-service dispute. It shows how a one-letter username can function as a valuable digital asset while its ownership depends on security and recovery processes operated by several separate companies.
First-order effects
- The @N owner loses control of an identifier described as worth $50,000, while Twitter must handle an ownership dispute over a name transferred through compromise.
- PayPal and GoDaddy face direct accountability for the account-access processes the report identifies as enabling the takeover.
Second-order effects
- Owners of high-value usernames and domains have reason to treat payment, registrar and social accounts as a linked security perimeter rather than independent accounts.
- Twitter's username-transfer and dispute processes become part of the practical risk for valuable handles, even when the reported breach originated with PayPal and GoDaddy.
Third-order effects
- As social identities acquire resale value, account recovery becomes a high-stakes control point: the weakest provider in a chain can determine ownership of assets held at another provider.
- The incident points toward demand for stronger, cross-service verification before identity changes can unlock domains, payment accounts or social-media identities.
The trend: Valuable online identities are turning account-recovery procedures at payment, domain and platform providers into a shared security boundary.