P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

DOJ says 42 months for fake White House explosion tweet; its $136 billion is a Dow claim, Reuters said S&P 500

The Department of Justice says a Syrian man was sentenced to 42 months in the Eastern District of Virginia for a conspiracy that hijacked a news agency's Twitter account on 23 April 2013. Its $136 billion market figure has no stated author, and 2013 reports gave it for the S&P 500, not the Dow.

By · LinkedIn · · 14 min read

42 months for a 12.4 year conspiracy, and a $136 billion figure with no author

The US Department of Justice says that on Thursday 29 October 2026 a federal district court in the Eastern District of Virginia sentenced a Syrian man to 42 months in prison for his central role in a hacking conspiracy "organized and led by members of former Syrian President Bashar Al Assad's inner circle, including the commander of Syria's General Intelligence Directorate" (the release's wording). The release dates the conspiracy "from as early as Aug. 24, 2011, to Jan. 31, 2024", a window of 4,543 days or 12.4 years (derived). The sentence is 3.5 years, which is 28 percent of that window (derived), and the best known act it describes, a false White House explosion post on 23 April 2013, is 4,937 days or 13.5 years before the sentence (derived). This briefing rests on the Department of Justice's press release 26-1289, read in full on 30 October 2026 (first at about 14:00 UTC) and read again before this briefing was finished. The defendant is a private individual and is not named here; the release and the press name him.

What that does not establish is most of what a reader would want to know about the case. The release prints no plea and no verdict, no counts or statutes for the defendant, no fine, no restitution order, no supervised release term and no arrest date. It says the defendant "had spent more than a decade as a fugitive" (the release's subheading) and gives no account of how he came before the court. It does not name the news agency whose Twitter account was used, and it says nothing about how that account was taken. Its most quoted number, $136 billion, is given with no author, no method and no time window.

The Department of Justice is both the prosecutor and the only source of the release, and the release quotes officials of the prosecuting bodies about the case. That is normal for a press release and it is not neutral reporting: where a figure or a motive is the Department's, this briefing says so. The press headline is firmer than the release. Help Net Security headlined its report "Assad regime hacker who caused $136 billion market drop sentenced to 42 months". The release's own words are that the defendant's actions "caused a flash crash in the U.S. stock market, resulting in a temporary $136 billion loss in the value of stocks making up the Dow Jones Industrial Average".

What the Department of Justice release states and what it does not. Source: US Department of Justice, press release 26-1289, dated 29 October 2026 and updated 30 October, read 30 October 2026.

QuestionStated by the Department of JusticeNot stated
The sentence42 months in prison, imposed by a federal district court in the Eastern District of Virginia.Plea or verdict, counts, fine, restitution, supervised release.
The conspiracyOrganised and led by members of the former Syrian President's inner circle, including the commander of Syria's General Intelligence Directorate, from as early as 24 August 2011 to 31 January 2024.Who among the inner circle did what; the defendant's exact role in the hoax post.
The hoax postA hijacked Twitter account of a widely respected news agency; a post on 23 April 2013 falsely claiming the US President was injured after two White House explosions.The agency's name; how the account was taken; the time of the post.
The market effectA temporary $136 billion flash crash in the value of stocks making up the Dow.Whose estimate; the method; the time window; any analysis of cause.
Others in the caseA coconspirator charged with the defendant remains a fugitive. A Syrian national then living in Germany was extradited and pleaded guilty on 28 September 2016, in a separate conspiracy.Sentences for others; any other custody; any other defendant.

What the 2013 reports say happened on 23 April

The release calls the target "a widely respected news agency". Contemporary reports name it. CBS San Francisco (carrying Associated Press copy, 23 April 2013) and CNBC (23 April 2013) both report that the Associated Press's Twitter account sent the false post, and that the agency said at once that it had been hacked. CBS adds that the attack on the agency's accounts "was preceded by phishing attempts on AP's corporate network", in its words. That is the agency's account as relayed in 2013, not a finding in the 2026 release, which says nothing about the method. The reports also say that a group calling itself the Syrian Electronic Army claimed responsibility and that this could not be corroborated at the time.

The timing in 2013 reports is tight. Reuters and CNBC put the false post at about 1:07 p.m. Eastern. CBS printed 10:12 a.m. Pacific, which is not the same minute, so this briefing uses the Reuters and CNBC time. CBS reported the Dow falling 143 points, from 14,697 to 14,554, which is 0.97 percent (derived), and then quickly recovering. CNBC said that within six minutes the Dow had recovered its losses and was trading with triple digit gains. Reuters reported that the analytics firm Dataminr alerted its clients that the account was probably hacked at 1:11 p.m., "just four minutes after" the post in its chief executive's words, and that by then the recovery was already under way. The alert cited another post, by a reporter inside the White House.

Drawn from CNBC (23 April 2013) and Reuters via Business Standard (25 April 2013), read 30 October 2026. The four minutes are Dataminr's own figure as Reuters printed it. CBS gave a different clock time for the post.

Two further details matter for defenders. CNBC reports that other major news agencies did not follow the false post, and that many had staff at the White House. Reuters reports that earlier hoaxes had come from newly created accounts that were easier to spot as suspect, whereas this account "is considered a trusted source" (Reuters's wording). The post worked because of whose account it came from, and the first alert came from looking at a second place, a reporter's post from inside the White House.

Where the $136 billion comes from: Dow stocks in 2026, the S&P 500 in 2013

The release uses the figure in three places: "a temporary $136 billion loss in the value of stocks making up the Dow Jones Industrial Average", "a temporary $136 billion flash crash in the value of stocks making up the Dow", and, in an official's quotation, a day that "temporarily erased $136 billion from U.S. investors". It does not say who calculated it, how, or over what window. The only place this briefing found the number's origin is the 2013 coverage. CNBC wrote on the day that "Reuters estimated that the temporary loss of market cap in the S&P 500 alone totaled $136.5 billion". A Reuters report two days later, republished by Business Standard, put it at "about $140 billion in market value on the S&P 500".

Drawn from the Department of Justice release of 29 October 2026, CBS and CNBC (23 April 2013) and Reuters via Business Standard (25 April 2013), read 30 October 2026. The 0.97 percent is derived.

So the release and the 2013 reports agree on a figure of about $136 billion for a temporary loss, and they attach it to different sets of stocks. The Dow is a narrower index than the S&P 500. This briefing cannot say which description is right, and it is not established that the release's wording is a deliberate restatement: it may be shorthand. What can be said is that the 2013 sources it could read give the number for the wider index, and that a loss the Dow made good within six minutes (CNBC's account) is a paper figure for a few minutes rather than money lost (an inference, not the Department's claim).

Two more points keep the number in proportion. First, the release says the defendant's actions "caused" the flash crash and prints no analysis of cause. Reuters in 2013 described automatic stop loss orders and traders pulling bids as amplifying the sell off, which describes a sell off amplified by market mechanics and does not contradict that the post started it. Second, the release says the defendant later "bragged" about the hack in an interview with Business Insider and quotes him: the Dow dropping "was our goal of that hack attack". That is the release's account of an interview this briefing did not read, and it is a statement of aim, not evidence of the size of the effect.

What else the release says the conspiracy did

The release says the defendant hacked approximately 47 Western media entities, businesses, NGOs, and US and allied government entities (a paraphrase of its wording). It lists "notable examples" of successful hacks, drawn from court filings, and the stated purposes of the conspiracy: to penalise the free press for reporting on the former Syrian government's atrocities, to cause fear and confusion among its opponents, to collect intelligence, and to attempt to cause mutiny or refusal of duty among members of the US military. The release does not mention ransomware. Extortion appears only in a separate case it describes, against the coconspirator and another Syrian national, which also covered money laundering, wire fraud and sanctions violations.

The release's notable examples. Source: US Department of Justice, press release 26-1289, read 30 October 2026. Derived figures are marked.

Victim or targetWhat the release saysNot stated, or derived
Company G, a supplier of content, ads and links to online publishersLost approximately $35,000 a day for approximately six months, according to court filings.Derived: about 180 days, so roughly $6 million in all. The release gives no total.
A global NGODeployed new network monitoring products costing around $250,000, retrained over 800 staff and upgraded its security, for total losses of $480,000.Derived: monitoring tools were 52 percent of the total. The other items are not priced.
A news agency's Twitter accountUsed for the post of 23 April 2013 about two White House explosions; a temporary $136 billion flash crash.The agency's name; how the account was taken.
The company hosting a US Marine Corps recruitment websiteVisitors were redirected to a server showing an image urging Marines to refuse their orders and fight alongside the Syrian Army; approximately 3,500 potential visitors saw it.The date of the attack; how the host was accessed; the time the page was up.
The White House social media pageTwo attempts to gain control by stealing usernames and passwords for White House staff email accounts. One succeeded, and the access was used in an unsuccessful effort to trick other staff into handing over the social media accounts.Which tool or lure was used; when.
The image shown in the Department of Justice release, as displayed to visitors of a US Marine Corps recruitment website after the redirect. The Department's own figure, reproduced with attribution; the content was created by the attackers. Read 30 October 2026.
Drawn from the Department of Justice release of 29 October 2026, read 30 October 2026. The 4,543 days, 4,937 days, 12.4 years and 28 percent are derived.

The dates matter for what they do not close. The complaint came 415 days after the post (derived, 23 April 2013 to 12 June 2014), the indictment 3.9 years after the complaint (derived), and the sentence 8.5 years after the indictment (derived). The release says the defendant was a fugitive for more than a decade and does not say when or where he was taken into custody. The coconspirator charged with him "remains a fugitive". The release links to two earlier Department of Justice releases about the separate case and the guilty plea. Both answered this briefing's fetch with an interstitial bot check page instead of the text, and this briefing did not try to get past it, so nothing here rests on them.

Headline claim against the record

Claims in coverage set against the release. Sources: US Department of Justice release 26-1289; Help Net Security, 30 October 2026; read 30 October 2026.

Claim in coverageWhat the record establishesWhat it does not establish
The hacker "caused" a $136 billion market drop (Help Net headline).The Department says the defendant's actions caused a temporary $136 billion flash crash in the value of Dow stocks.Cause by the post alone; the author and method of the figure; that any of it was a realised loss.
The hijacked account was a news agency's.The Department says so, without a name. CBS and CNBC in 2013 name the Associated Press.That the release itself identifies the agency.
The scheme ran until January 2024.The release says as early as 24 August 2011 to 31 January 2024.Which acts fall in which year; the defendant's own period of activity.
The defendant was on the run for a decade.The release says he spent more than a decade as a fugitive.The arrest date, place or route to court.
The defendant pleaded or was convicted.Nothing in the release.A plea, a verdict or the counts.

Technical details

The Department of Justice release prints no technical artifacts: no domains, addresses, hashes, tools, lures, account names or log lines. Nothing below is an indicator of compromise for 2026. The two blocks hold the only wording the sources print that a defender can use as a pattern. Below is the text of the false post, as CBS printed it on 23 April 2013. CNBC's copy capitalises "Injured", and Reuters noted differences from the agency's house style, such as capitals and "Barack Obama" for "President Obama". A defender can use this as an example of a claim with no named source, no link and a style break, not as a signature.

Text
Breaking: Two Explosions in the White House and Barack Obama is injured.
Text of the false post, from CBS San Francisco, 23 April 2013, read 30 October 2026.

The release describes the White House attempts in one line. It names the technique and nothing else. Defenders should read it as: email accounts of staff who can reach a social media account are the route, so they need the same protection as the account.

Text
stealing usernames and passwords for the email accounts of White House staff
Wording from the Department of Justice release of 29 October 2026, read 30 October 2026.

What to do, in order

The release gives no defender guidance. The list below is this site's reading of what the record shows went wrong, ranked by how directly each step would have blocked or blunted the 2013 hoax, and it is advice, not the Department's. No product is recommended.

Take this with you

Ranked checklist for newsrooms, brands and trading desks

  • Put hardware security keys on every social media account that can publish for the organisation, and on the email accounts that can reset them. The release's White House example turned on stolen email credentials.
  • Train staff who hold publishing credentials to recognise phishing aimed at them. CBS reported phishing attempts on the agency's corporate network before its accounts were hit.
  • Keep a verified account recovery contact at the platform and a named after hours escalation, so a hijack can be reported and the account frozen in minutes, not hours.
  • Prepare an incident post template and approval, so the correction (this account has been hacked, the report is false) is ready before it is needed.
  • Cut the number of people and tools with publishing rights, and review them every quarter.
  • Set a rule for desks and algorithms that a breaking claim from one account needs a second independent source before anyone trades. Reuters quoted an analytics chief executive in 2013: "I would never recommend that anyone trades on a single tweet".
  • Test the rule with a drill that uses a plausible false post from a trusted looking account, and time how long the second check takes.

None of this needs a new product. In 2013 the correction came from the agency itself and the first alert, per Reuters, came four minutes after the post. The gap between those four minutes and the minutes the market needed is the whole case for a second source rule.

If a single post from a trusted account can move prices for minutes, what is the second check at your desk or on your account, who owns it, and how long does it take?

Key facts

Sources

  1. PrimaryPress release 26-1289, 'Syrian Man Sentenced for Wide Ranging Hacking Conspiracy Conducted on Behalf of the Bashar Al Assad Regime', dated 29 October 2026 and updated 30 October: the sentence, the conspiracy window, the examples, the $136 billion statements, the dates and the other defendants. The primary, read in full three timesUS Department of Justice, Office of Public Affairsaccessed 2026-10-30
  2. Reported byHelp Net Security, 30 October 2026, 'Assad regime hacker who caused $136 billion market drop sentenced to 42 months': the press reading set against the release, and the link to the release. SecondaryHelp Net Securityaccessed 2026-10-30
  3. Reported byCBS San Francisco, 23 April 2013, 'Phony AP Tweet Says President Hurt In White House Explosions; Stocks Bounce': the post text, the Dow levels, the phishing statement and the Syrian Electronic Army claim. Secondary, contemporaryCBS San Francisco (with Associated Press copy)accessed 2026-10-30
  4. Reported byCNBC, 23 April 2013, 'False Rumor of Explosion at White House Causes Stocks to Briefly Plunge; AP Confirms Its Twitter Feed Was Hacked': the 1:07 p.m. time, the six minute recovery and Reuters's $136.5 billion S&P 500 estimate. Secondary, contemporaryCNBCaccessed 2026-10-30
  5. Reported byReuters, 'Hoax tweet tests firms that filter social media for Wall Street', republished by Business Standard on 25 April 2013: the $140 billion S&P 500 wording, the 1:07 and 1:11 p.m. times, the trusted source point and the amplification by stop loss orders. Secondary, contemporaryReuters, via Business Standardaccessed 2026-10-30

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.