← All articles

Total current articles · 3,480

2024 U.S. Intelligence Leak on Israeli Strike Plans

Published

01In brief

The 2024 U.S. intelligence leak on Israeli strike plans was the unauthorized online disclosure of two classified U.S. documents describing Israeli preparations for a possible retaliatory strike on Iran. The documents, dated October 15 and 16, appeared on Telegram on October 17, after Iran’s October 1 missile attack on Israel. Their reported details included air-force exercises and movements of munitions, but they did not identify potential targets. The disclosure prompted U.S. investigations and the prosecution of CIA employee Asif William Rahman, who pleaded guilty and was sentenced to 37 months in prison. Contemporary and later accounts differed over whether the leak delayed Israel’s strike.

02Background

The leak came amid expectations of an Israeli response to Iran’s October 1, 2024, ballistic-missile attack on Israel. The Biden administration was trying to persuade Israel to avoid Iranian nuclear sites or energy facilities.[7] The leaked documents described U.S. observations of Israeli military activity on October 15–16, as preparations for a possible counterstrike were under way.[2][3]

The documents were dated October 15 and 16 and were marked “Top Secret” and for Five Eyes viewing, according to contemporaneous reporting. They were presented as U.S. intelligence assessments rather than Israeli operational documents, and the satellite images they referenced were not included in the files that circulated publicly.[3][4]

03Course of Events

Two documents appeared on the Middle East Spectator Telegram channel on October 17, 2024, and were subsequently circulated on X. They were characterized as intended for the United States and its Five Eyes partners: Australia, Canada, New Zealand, and the United Kingdom.[1][2] The channel said it had received the material from a source in the U.S. intelligence community, but its account of how the files reached it was not independently verified in the cited reporting.[9] The channel operator later denied being the original source of the leak and disassociated the channel from the party responsible for disseminating the documents.[1][3]

The first document was described as a National Geospatial-Intelligence Agency assessment based on satellite imagery. It reportedly covered Israeli Air Force preparations, including drone surveillance activity in Iran, an aerial-refueling exercise on October 15, and practice of search-and-rescue operations. The second document was described as apparently based on National Security Agency reporting and concerned air drills, intelligence activity, and weapons movements.[1][4] These were descriptions of the leaked assessments, not independent confirmation of the activities they reported.[1]

One account of the leak said the documents alleged that Israel transferred 16 “Golden Horizon” missiles and relocated 40 ROCKS IS02 stand-off air-to-surface missiles. They also reportedly described two air drills on October 15–16 that included air-to-air refueling practice, and concealment screens over six F-15I fighters; the weapon identifications were qualified as uncertain.[1] Other reporting described preparations involving long-range air-launched ballistic missiles, air-to-surface missiles, refueling aircraft, and support aircraft, while noting that the documents did not name possible targets.[4]

Early reporting differed over how securely the documents’ authenticity had been established. Some accounts said investigators were still working to authenticate the files; other reporting, citing Israel’s Kan public broadcaster, said U.S. officials had confirmed their authenticity and apologized to Israel. On October 21, White House Press Secretary Karine Jean-Pierre declined to confirm whether the documents were authentic or classified and said officials could not yet say whether the incident was a leak or a hack.[10][11][3]

The U.S. government announced investigations in October. On October 21, Jean-Pierre said the administration was very concerned and that the appropriate authorities were looking into the matter, but provided no result. The State Department’s Vedant Patel referred questions to the Department of Defense, the Intelligence Community, and the Department of Justice; he said he did not expect the reports to affect Secretary of State Antony Blinken’s trip or its objectives.[11][12] The FBI confirmed on October 22 that it was investigating with the Department of Defense and the intelligence community. At that stage, investigators were working to authenticate the files and identify who had access; an insider leak was described as a working theory, not a confirmed finding.[10]

In November, Asif William Rahman, a CIA employee, was identified as the person accused of leaking the documents. A grand jury indicted him on November 7, 2024, on two counts involving the retention and transmission of national-defense information; the FBI arrested him in Cambodia on November 12, and the case was brought in federal court in Virginia.[2][5] Court records said Rahman printed two documents on October 17 concerning a U.S. ally’s planned action against a foreign adversary, removed and photographed them, and sent them to people he knew were not authorized to receive them. By the following day, the documents had appeared publicly on multiple social-media platforms with their classification markings.[5]

The case also involved other classified material. Court records said Rahman printed and mishandled additional secret and top-secret documents during 2024, including documents he took home, reproduced, altered, or shared with unauthorized people. He took steps to conceal his activity, including editing or deleting material on personal devices and destroying electronic devices.[5] In January 2025 he pleaded guilty to retaining and transmitting national-defense information; on June 11, 2025, he was sentenced to 37 months in prison. He also admitted leaking more than a dozen additional classified documents whose contents were not made public.[6][13]

04Aftermath

The Biden administration said it was very concerned and was investigating the unauthorized release.[11] A U.S. official said contemporaneously that the leak would not influence Israel’s operational plans.[3] The documents offered only a partial view of the intelligence picture: satellite collection would not readily reveal cyberattacks or sabotage on the ground in Iran, so the disclosed material might have represented only part of what the United States had collected.[4]

Israel carried out a strike on Iran on October 26, targeting air defenses and other military infrastructure.[4] Reporting on the leak’s possible effect changed over time. The early U.S. assessment said it would not influence Israeli plans.[3] A senior Israeli security official later denied any connection between the leak and the timing, saying no final attack date had been set and then postponed.[8] Later reports attributed a delay to the leak, including an account that Israel altered its operational plan after the disclosure.[7][13] The cited accounts do not establish a single settled causal conclusion about whether the disclosure changed the timing of Israel’s response.

05Historiography

The episode is documented through several kinds of evidence: the publicly circulated documents and their media descriptions, official statements about the investigation, and later court proceedings concerning Rahman. Those records answer different questions. The White House initially would not confirm the files’ authenticity or classification.[11] Later coverage of the criminal case documented Rahman’s guilty plea and his 37-month sentence for transmitting national-defense information.[5][6]

The precise route by which the files were disseminated online and the effect of the disclosure on Israeli operational timing were treated differently across accounts. Middle East Spectator’s claim about how it obtained the files was not independently verified in the cited coverage.[9] An early U.S. assessment said the leak would not influence Israeli plans, while an Israeli security official denied that a final date had been postponed.[3][8] Later reports attributed a delay to the disclosure.[7][13] These distinctions separate the established criminal case from unresolved claims about the leak’s operational consequences.

Sources

  1. 1FDD's Long War Journal, Analysis: Leaks and spy rings merely delay the inevitable Israeli operation, accessed on October 26, 2026.
  2. 2Ynet, Pentagon documents leaker arrested: “CIA agent”, accessed on October 26, 2026.
  3. 3Jewish News Syndicate, US investigating leak of classified intel on Israel's Iran attack plans, accessed on October 26, 2026.
  4. 4Jewish Virtual Library, Military Options Against Iran, accessed on October 26, 2026.
  5. 5Jewish News Syndicate, Former CIA analyst admits leaking secret info about Israeli response to Iran, accessed on October 26, 2026.
  6. 6Ynet, U.S.: 37 months in prison for leaking Pentagon documents about an Israeli strike in Iran, accessed on October 26, 2026.
  7. 7Ynet, Pentagon documents leaker pleads guilty: expected sentence—up to 6.5 years in prison, accessed on October 26, 2026.
  8. 8Maariv, Senior security official reveals: the whole truth about the response plan for Iran, accessed on October 26, 2026.
  9. 9The Jerusalem Post, US documents showing Israel attack plans on Iran leaked - report, accessed on October 26, 2026.
  10. 10Jewish News Syndicate, FBI confirms probe into leaked intel on IAF Iran strike prep, accessed on October 26, 2026.
  11. 11U.S. National Archives, Press Briefing by Press Secretary Karine Jean-Pierre, October 21, 2024, accessed on October 26, 2026.
  12. 12U.S. Department of State, Department Press Briefing – October 21, 2024, accessed on October 26, 2026.
  13. 13Mako, CIA man who leaked Israel’s attack plans sentenced to 3 years in prison, accessed on October 26, 2026.

IsraelPedia Question & Answers

  • What was the 2024 U.S. intelligence leak on Israeli strike plans?

    The 2024 U.S. intelligence leak on Israeli strike plans was the unauthorized online disclosure of two classified U.S. documents describing Israeli preparations for a possible retaliatory strike on Iran. The documents appeared on Telegram on October 17, 2024, after Iran’s October 1 missile attack on Israel. The disclosure prompted U.S. investigations and the prosecution of CIA employee Asif William Rahman.

  • What did the leaked documents say about Israel’s preparations?

    The leaked assessments reportedly described Israeli Air Force preparations, including drone surveillance activity in Iran, aerial-refueling exercises, search-and-rescue practice, air drills, and movements of weapons and support aircraft. Some reported weapon identifications were qualified as uncertain. The documents did not identify possible targets, and their descriptions were not independent confirmation that the reported activities had taken place.

  • How did the U.S. intelligence documents become public?

    Two documents appeared on the Middle East Spectator Telegram channel on October 17, 2024, and were later circulated on X. The channel said it received the material from a source in the U.S. intelligence community, but that account was not independently verified in the cited reporting. The channel operator later denied being the original source of the leak.

  • Who was prosecuted for leaking the Israeli strike-plan documents?

    CIA employee Asif William Rahman was prosecuted for retaining and transmitting national-defense information, including the documents concerning a U.S. ally’s planned action against a foreign adversary. He was arrested in Cambodia on November 12, 2024, after a grand jury indicted him on two counts. Rahman pleaded guilty in January 2025 and was sentenced to 37 months in prison on June 11, 2025.

  • Did the leak delay Israel’s strike on Iran?

    The cited accounts do not establish whether the leak changed the timing of Israel’s response. Israel struck Iran on October 26, 2024. An early U.S. assessment said the leak would not influence Israeli plans, and a senior Israeli security official later denied that a final attack date had been postponed. Later reports attributed a delay to the disclosure.