Journalist lost his job as a WSJ foreign correspondent after what was likely a state sponsored hack that led to an investigation of conduct with his sources
Jay Solomon / Columbia Journalism Review : Tweets: @cjr , @nxthompson , @cjr , @nedprice , and @ahmed Tweets: @cjr : “The phone call set off a brutal 48 hours in which I eventually lost my job.” http://www.cjr.org/... Nicholas Thompson / @nxthompson : Jay Solomon tells his side of the story. The lessons: * be careful in all reporting and know you can get hacked * talk to your editors * don't let anyone think you're mixed up in the arms trade. http://www.cjr.org/... @cjr : How hacked emails and a yacht in Monaco ended my career at WSJ http://www.cjr.org/... http://twitter.com/... Ned Price / @nedprice : Interesting piece w Jay Solomon's tips on how to avoid his predicament. Here's another: Don't allow even the impression you're taking part in the intl arms trade with a source. http://www.cjr.org/... Ahmed Al Omran / @ahmed : Former @WSJ reporter @jaysolomon on how spending time with shadowy sources on a yacht in Monaco sparked a chain of events that cost him his job http://www.cjr.org/...
Context & Ripple Effects
Jay Solomon's first-person account is unusual because the breach never became a leak: emails taken in what was likely a state-sponsored hack stayed in adversarial hands and instead set off a brutal internal reckoning, with the Wall Street Journal investigating whether his dealings with sources in the international arms trade — symbolized by a yacht in Monaco — crossed ethical lines. He lost his job within roughly 48 hours of the phone call that started it.
The story fits a documented pattern in the surrounding coverage: Citizen Lab staff, whose exposés target government hacking-tool vendors like NSO, describe meetings likely arranged to extract compromising quotes from them — adversaries working to entrap journalists directly rather than just surveil them. Solomon's case shows the quieter variant: stolen material used to activate a newsroom's own ethics machinery against its reporter.
First-order effects
- Solomon is out at the Wall Street Journal, and the paper's investigation into his source conduct was triggered not by published leaks but by emails accessed in the breach.
- Nicholas Thompson's publicized lessons — know you can get hacked, talk to your editors, never appear mixed up in what you cover — become the immediate playbook other foreign correspondents are measured against.
Second-order effects
- Newsrooms now have an incentive to treat reporters' inboxes as an attack surface on par with their sources' security, since a rival or state actor can end a career by routing stolen correspondence to editors rather than to the public.
- Sources in sensitive beats like arms dealing face a new risk calculus: contact with a targeted correspondent can be reconstructed from seized email, chilling relationships the reporter spent years building.
Third-order effects
- If the pattern holds, state actors gain a deniable tool for removing individual correspondents — no publication, no lawsuit, just an ethics probe fed by hacked material — pushing newsrooms toward formalized operational security and editor check-ins as standard practice for high-risk beats.
- The distinction between hacking a journalist to expose them and hacking them to discredit them blurs, forcing outlets to build verification norms for internally surfaced 'evidence' of misconduct.
The trend: State-linked hacking is shifting from leaking journalists' stolen communications to deploying them quietly inside newsrooms, turning source relationships themselves into the attack surface.