Iran-Linked Freezer Hacks, Active *sshole Exploit

Iran-Linked Freezer Hacks Shake European Supply Chains

France’s foreign minister publicly accused Iran of launching at least two coordinated cyber waves against industrial refrigeration and freezer units. The attacks hit grocery stores and blood banks across France and rippled into neighboring European markets. The minister cited intelligence that linked the intrusion tools to Iranian state actors. The sabotage disrupted cold-chain logistics and threatened perishable inventory. Cold-chain operators reported temperature excursions lasting hours. Some blood banks triggered emergency protocols to preserve plasma viability. The incidents forced retailers to reroute stock and activate backup generators. The French government pledged to bolster cyber defenses for critical infrastructure. The attribution marks a rare instance of a nation-state targeting food safety hardware.

*sshole Vulnerability Under Active Exploitation in the Wild

Security researchers identified a flaw dubbed “*sshole” that grants unauthenticated SSH access to vulnerable Linux devices. The bug bypasses standard authentication checks and opens a remote shell. Exploit code circulates on underground forums, and threat actors are already leveraging it against exposed servers. The vulnerability affects a broad range of Linux distributions that ship the flawed SSH daemon. Patching requires updating the affected package and restarting the service. Vendors released advisory notices this week, but many operators have not yet applied the fix. Active exploitation raises the stakes for cloud providers, IoT deployments, and on-premise data centers. Industry analysts warn that the rapid weaponization mirrors previous zero‑day campaigns. The open‑source nature of the SSH stack means the flaw can propagate quickly. Organizations that neglect regular patch cycles now face a credible path to full system compromise.

Claude Code’s “Do Not Ask Again” Prompt Leaks Secrets on GitHub

Anthropic’s Claude Code integration introduced a “Do not ask again” option in its IDE assistant. When users enabled the shortcut, the model began inserting passwords, API keys, and other credentials into code suggestions without prompting. The leaked snippets surfaced across public GitHub repositories. The issue stems from the assistant caching prior user inputs and reusing them indiscriminately. Developers reported seeing their private tokens appear in unrelated projects. Anthropic issued a quick fix that disables the shortcut by default and adds a warning banner. Security teams scrambled to purge the exposed secrets from version control histories. The incident underscores the risk of AI‑assisted coding tools that retain sensitive context. Companies now audit AI‑generated code for credential leakage before merging changes.

Industry Response and the Growing Attack Surface

Vendors across the supply chain announced emergency patches and hardening guides. Linux distro maintainers published updated SSH packages within 48 hours of the *sshole disclosure. Refrigeration manufacturers rolled out firmware updates to validate command integrity. Regulators in the EU cited the freezer attacks as a breach of the NIS2 directive, which mandates robust cybersecurity for essential services. France’s cybersecurity agency opened a joint investigation with its Iranian counterpart, though diplomatic channels remain strained. AI tool providers faced renewed scrutiny from privacy advocates. Anthropic pledged an independent audit of Claude Code’s data handling. The broader tech community is debating mandatory credential‑scrubbing layers for AI assistants.

What to Watch

Track the French government’s formal attribution report, which will detail the technical indicators linking Iran to the freezer breaches. Monitor Linux distribution release notes for the next *sshole patch cycle and adoption metrics across cloud providers. Follow Anthropic’s audit results and any policy changes to AI‑assistant credential management. The convergence of state‑sponsored sabotage, zero‑day exploitation, and AI‑driven leaks suggests a tightening regulatory focus on supply‑chain resilience.