Iranian lethal plotting has surged inside and outside the United States, and honestly, the warning signs aren't subtle anymore.
On November 18, 2026, Director of National Intelligence Jay Clayton told the House Homeland Security Committee that threats from Tehran against Americans have substantially increased. Speaking during a hearing titled "Worldwide Threats to the Homeland: 25 Years After 9/11," Clayton made it plain that U.S. personnel abroad and people at home face greater danger.
Anyone scanning basic news summaries sees the headline quote and moves on. That's a mistake. To understand what's actually happening, you have to connect Clayton's testimony to nine months of military strikes since February 2026, fresh federal sentencing in New York, cyber warnings from Homeland Security, and sharp disagreements inside Washington over how imminent some of these threats really are.
What Iranian Lethal Plotting Actually Looks Like on the Ground
When intelligence officials talk about lethal plotting, people often picture a single dramatic movie scene. Real counterterrorism work looks messier, slower, and more varied.
It spans regional military retaliation, foreign assassination or kidnapping schemes, pressure against dissidents, and covert networks operating across borders. Following the U.S. and Israeli strikes on Iran that began in February 2026, tensions in the Middle East have stayed elevated for more than eight months. By late October 2026, intelligence reporting already pointed to heightened efforts targeting U.S. personnel in the Middle East and elsewhere, with some plots assessed as reaching advanced stages.
Look at the Gulf theater in mid-November 2026. According to U.S. Central Command (CENTCOM) statements reported this week, Iranian forces launched one-way attack drones toward Bahrain on November 17 that were intercepted without damage or injury, after earlier strikes targeted radar and early warning assets there on November 13 and November 15. Meanwhile, in Europe, North Macedonia's National Security Agency announced on November 17 that it had disrupted a network linked to Iran in coordination with Greek intelligence.
FBI Deputy Director Christopher Raia told lawmakers on November 18 that the bureau had revamped its Iranian threat mission center and racked up public counter-plotting wins, particularly around schemes targeting dissidents. That detail matters. Tehran has long used intimidation, surveillance, and recruitment of intermediaries to reach critics and officials beyond its borders, even when local operatives get tripped up by sloppy tradecraft or undercover law enforcement.
The Asif Merchant Case Shows How Recruitment Works
A concrete example hit federal court this week. On November 17, 2026, U.S. District Judge Eric Komitee sentenced 48-year-old Pakistani national Asif Merchant to 330 months—more than 27 years—in prison after his earlier conviction on murder-for-hire and attempted terrorism charges tied to a 2024 plot.
According to the U.S. Department of Justice, Merchant met with people he thought were hitmen, paid a $5,000 advance with help from overseas relatives, and searched online and on Google Maps for rally details connected to Donald Trump. The supposed hitmen were undercover FBI agents, and Merchant was arrested in Texas in July 2024.
At trial, Merchant claimed he acted under pressure from an Islamic Revolutionary Guard Corps (IRGC) contact out of fear for relatives in Tehran and didn't expect anyone to die. Attorney General Todd Blanche called the case a direct threat against President Trump. Either way, the mechanics are instructive: foreign handlers often try to distance themselves by using third-country intermediaries, local cash, and plausible deniability.
Why Washington Is Split Over the Dirty Bomb Claims
If you only read one wire report, you might walk away thinking a radiological attack on Washington, D.C., is practically around the corner. Slow down. Look closely at what officials actually said.
Reports emerged this week citing U.S. intelligence assessments about a possible Iranian plan involving a dirty bomb in Washington. A dirty bomb uses conventional explosives to scatter radioactive material rather than triggering a nuclear detonation. Speaking to reporters in the Philippines on November 17, President Trump said his administration takes the possibility very seriously and warned of severe consequences if an attack occurred.
Yet when pressed during the November 18 House hearing, DNI Clayton declined to discuss specific intelligence reporting on the alleged plot. He noted more broadly that "civilian mass destruction threats" have existed for a long time. And on November 18, Secretary of State Marco Rubio told reporters while traveling with Trump in Asia that he did not believe there was an imminent threat to the U.S. capital, echoing earlier White House messaging that there were no credible threats to the homeland at that moment.
Iranian officials rejected the reporting outright. Foreign Minister Abbas Araghchi dismissed media claims about plots in D.C. as propaganda, and Foreign Ministry spokesman Esmaeil Baghaei called the allegations baseless and warned of a strong response to any new U.S. strikes.
Here's my take after watching how intelligence leaks and wartime rhetoric play out: an intelligence assessment of a possible plot is not the same thing as a confirmed or imminent attack. Governments routinely weigh worst-case scenarios, leak-driven narratives fly fast during active military conflict, and adversaries use denials to shape public opinion. Treating every rumor as inevitable creates panic; brushing off state-backed lethal plotting as mere noise leaves people unprepared.
Cyber Pressure and Critical Infrastructure Risks
Lethal plotting doesn't sit in a vacuum. During the same November 18 hearing, Homeland Security Secretary Markwayne Mullin warned that Iran-linked hackers are targeting U.S. critical infrastructure—specifically energy, water, and transportation systems.
Why pair physical plots with cyber pressure? Because asymmetric adversaries love multiplying friction. Even when a kinetic plot fails or a cyber intrusion stops short of a catastrophic outage, probing energy grids, water utilities, or transit networks tests defenses and keeps security teams stretched thin.
In my experience looking at security advisories, organizations often get tripped up by two classic mistakes:
- Treating cyber and physical security as separate silos. A breach into operational technology or vendor accounts can support physical reconnaissance or disrupt local response times.
- Focusing only on exotic attacks while ignoring basic hygiene. Most real-world intrusions still exploit unpatched software, weak identity controls, or phishing—not Hollywood zero-days.
What You Can Actually Do Right Now
You can't control foreign intelligence agencies or Middle East escalation, and trying to doom-scroll every breaking alert will just fry your nervous system. You can tighten up your own everyday security habits and verify what you read.
- Check multiple primary sources before sharing breaking threat claims. Look for official statements from agencies like the U.S. Department of Justice or U.S. Central Command, and compare reporting across outlets rather than reacting to a single headline.
- Lock down personal accounts and devices. Turn on multifactor authentication (ideally a hardware security key or authenticator app rather than SMS alone), keep operating systems updated, and watch out for spear-phishing emails or texts pretending to come from banks, employers, or government agencies.
- If you travel or work in high-risk regions, register and follow official advisories. Keep up with State Department travel guidance, know local emergency contacts, and avoid sharing real-time location details publicly.
- If you manage infrastructure, small business systems, or community facilities, run a practical basics audit. Verify backups are offline and tested, segment critical networks, and review who has administrative access today.
Stay sharp, verify before you panic, and build habits that hold up whether headlines calm down or heat up.