A war of missiles and messages.

The CyberWire Daily episode on April 1st, 2026, delivers a high-stakes overview of the evolving cyber conflict between Iran, Israel, and the U.S., where cyber operations are increasingly used as tools of psychological warfare and strategic disruption. From fake emergency texts in Israel to supply chain attacks targeting Axios NPM and Cisco’s internal systems, the episode highlights how state and non-state actors are exploiting digital vulnerabilities with growing sophistication. A leaked Claude code client reveals unprecedented system access capabilities, while the DoD’s zero-trust rollout faces delays despite massive funding. Privacy concerns mount as Perplexity faces a class action suit over data sharing, and the FBI warns against foreign-developed mobile apps. The episode also features a deep dive with Christy Wyatt of Absolute Security, who reframes cyber risk as a business continuity issue, advocating for proactive resilience strategies—especially in the age of AI—where rapid recovery is critical. Her company’s 'Rehydrate Ready' initiative emphasizes embedding recovery capabilities into firmware to minimize downtime. The episode closes with a community surveillance program in Milpitas, California, that distributes free doorbells to promote crime deterrence, raising privacy and surveillance concerns. Key takeaways include: 1) Cyber operations are now central to geopolitical conflict, blending military strategy with psychological manipulation; 2) Supply chain attacks are escalating, with widespread impact across software ecosystems; 3) AI is amplifying both innovation and risk, increasing system fragility; 4) Business continuity must be prioritized alongside prevention, with recovery capabilities embedded in infrastructure; 5) Proactive resilience—like remote device healing—can drastically reduce downtime; 6) Privacy risks are growing with AI and data-sharing practices; 7) Public surveillance programs, while well-intentioned, risk normalizing neighborhood-scale monitoring; 8) Cyber resilience requires cross-functional planning and regular rehearsal, not just technical controls.