jain.com — data centers, connectivity and security, analyzed daily

Tag: NSA

  • Russia-Linked Zimbra Exploit Takes 90 Days of Email on View. Patching Is the Defense

    Russia-Linked Zimbra Exploit Takes 90 Days of Email on View. Patching Is the Defense

    TL;DR · 30-second read

    The Short Version

    Hackers backed by the Russian state have spent about a year breaking into organizations through a popular email system called Zimbra, according to the United States National Security Agency and 26 partner agencies across 16 countries.

    The worrying part: nobody has to click anything. Simply opening a booby-trapped email on an out-of-date system lets the attackers copy the last three months of messages and the organization’s full staff contact list.

    The fix is ordinary but urgent: install the software update, then check whether anything was already taken.

    On July 23, 2026, the National Security Agency (NSA) said in a press release that it and 26 partner agencies from 16 countries had published a joint Cybersecurity Advisory titled “Russian State-Supported Cyber Actors Conduct Phishing Campaign Targeting Users of Zimbra Collaboration Suite.” The advisory attributes the activity to LAUNDRY BEAR, a Russian state-supported advanced persistent threat group, which has targeted Zimbra Collaboration Suite (ZCS) users across U.S. and allied government and commercial networks since July 2025.

    The group uses a custom tool the agencies call “Ulej” to deliver an exploit that triggers automatically when a user views a malicious email in a vulnerable version of Zimbra’s webmail. The flaw, CVE-2025-66376, was a zero-day when first used and is still being exploited on unpatched servers. The exploit attempts to exfiltrate the organization’s email directory, the last 90 days of the victim’s communications, and other sensitive information.

    Executive Summary

    A coalition of intelligence and cybersecurity agencies spanning the Five Eyes and much of NATO Europe has put its name to a single warning: a Russian state-supported group has been quietly harvesting email from Zimbra servers for roughly a year, and it is still succeeding wherever administrators have not patched. The co-sealing list runs from the FBI and CISA to the UK’s National Cyber Security Centre, France’s ANSSI, both Dutch intelligence services, and agencies in Poland, Estonia, Finland, Sweden and Moldova.

    What makes this advisory operationally important is the delivery mechanism. The exploit is “view-based”: it fires when a user opens the message in webmail, with no link to click and no attachment to run. That removes the human judgement that most phishing defenses rely on and turns the problem into one of patch management and network monitoring. For any organization that runs its own mail infrastructure, including data center, connectivity and cloud operators, the question is no longer whether staff can spot a suspicious email but whether the server was patched before the message arrived.

    The advisory also documents what the exfiltration looks like on the network and lists indicators of compromise, the specific technical fingerprints defenders can search for, along with remediation steps. That matters because patching closes the door going forward but does nothing about mail that has already left.

    When Viewing Is Enough, Training Stops Being the Control

    Most organizations treat phishing as a people problem: teach staff not to click unfamiliar links or open unexpected attachments, and run simulated campaigns to measure progress. The exploit described in this advisory sidesteps that model entirely. According to the NSA, it “triggers automatically when a user views a malicious email within a vulnerable version of the webmail service.” A well-trained employee who opens a plausible-looking message to decide whether it is suspicious has already triggered it.

    That shifts the controlling variable from user behavior to software version. On a patched Zimbra server, the message is inert; on an unpatched one, reading it is the compromise. The NSA states the exploit “is still used to successfully exploit ZCS instances that are still unpatched,” which tells defenders two things: the attackers are getting returns from this technique roughly a year after the campaign began in July 2025, and the population of vulnerable servers is large enough to keep them doing it. Awareness training remains useful against the wider phishing threat, but against this specific campaign the effective defense is patch speed, followed by hunting for signs of earlier theft.

    The people most affected are administrators of self-managed mail systems. When email runs as a cloud service, the provider patches the server. When an organization runs Zimbra on its own hardware or virtual machines, that job falls to an internal team competing with every other maintenance priority, and a webmail server that “still works” is easy to defer.

    What 90 Days of Mail and a Directory Are Worth to an Attacker

    The exploit targets three things: the organization’s email directory, the last 90 days of the victim’s communications, and “other sensitive information.” Each has distinct value. The directory is a map of the organization: names, roles and addresses that make the next round of targeted phishing more convincing. Ninety days of mail captures current projects, vendor relationships, internal decisions and, frequently, credentials or configuration details that people send to one another despite policy.

    For operators of physical and digital infrastructure, the stakes are concrete. Email is where maintenance windows are scheduled, where network change requests are discussed, where customer contracts and site access arrangements are negotiated. A three-month window of that traffic from one well-placed mailbox can give an intelligence service a detailed view of how an operator runs and who it serves, without ever touching the operational network itself.

    The directory theft also means the damage can compound. Contacts harvested from one victim become credible senders and plausible targets for the next, which is one reason a campaign of this kind can keep expanding across “U.S. and allied government and commercial networks,” as the release describes.

    A 27-Agency Signal on Breadth and Priority

    Joint advisories are common; one carrying the seals of 27 agencies across 16 countries is not routine. The list includes foreign intelligence services, military counterintelligence and financial authorities (the U.S. Department of the Treasury) alongside the civilian cyber agencies that usually issue these warnings. The release does not explain why each agency joined, and the breadth should not be over-read as a measure of damage. It does indicate that the activity has been observed, or is considered relevant, across a wide set of allied governments.

    The advisory’s technical focus is also telling. The NSA says it “characterizes the network activity occurring during the exfiltration stage.” That is aimed at defenders who may already be compromised: an organization that patched in, say, the last few months still needs to know whether data left its network before then. Egress logs, proxy records and firewall data from the preceding year are the relevant evidence, and teams that do not retain those logs long enough will struggle to answer the question.

    The Practical Sequence for Zimbra Operators

    The advisory implies a clear order of work. First, confirm that every Zimbra instance, including forgotten test or regional servers, is on a version that addresses CVE-2025-66376. Second, search mail and network logs for the indicators of compromise the advisory lists. Third, if any match, follow the remediation steps in the full report and assume the directory and recent mail of affected users are in hostile hands.

    That third step has consequences beyond IT. If 90 days of correspondence has been exfiltrated, legal, contractual and customer-notification questions follow. For infrastructure providers whose customers include government agencies or regulated industries, a confirmed compromise of internal mail may need to be treated as a customer-facing incident, not just an internal clean-up.

    Background

    Email servers have long been a favored target for state-backed intelligence operations because a single compromised mailbox can reveal an organization’s contacts, plans and internal discussions. Self-hosted webmail platforms such as Zimbra are especially exposed: they sit on the public internet by design, and keeping them patched depends entirely on the operator’s own team.

    Joint advisories from the NSA, CISA, FBI and allied agencies are the main channel through which Western governments share technical detail about state-sponsored campaigns with the private sector. They typically include indicators of compromise and mitigation guidance so that organizations can check their own systems, and a large number of co-sealing agencies generally reflects broad concern among allied governments about the activity described.

    Sources

    Source: NSA and Partners Alert Zimbra Collaboration Suite Users of a Russian State-Supported Phishing Campaign — National Security Agency press release announcing a joint advisory on LAUNDRY BEAR’s exploitation of CVE-2025-66376 in Zimbra webmail.

  • US Warns State-Linked Hackers Target Network Gear; NSA Issues Router Hygiene Guidance

    US Warns State-Linked Hackers Target Network Gear; NSA Issues Router Hygiene Guidance

    US government authorities issued a public warning that state-linked threat actors are actively targeting vulnerable networking devices — including routers, switches and other edge gear — and the National Security Agency published accompanying router hygiene guidance, according to a July 13, 2026 Cybersecurity Dive report.

    The advisory is directed at operators of enterprise, small-business and home networks whose exposed devices can be recruited into espionage and pre-positioning campaigns.

    Executive Summary

    The joint messaging elevates a long-running concern into a formal public alert: perimeter networking devices, not just servers and endpoints, are a preferred entry point for state-linked intrusion sets. NSA’s router hygiene guidance is the practical companion — a checklist of configuration and maintenance steps operators are expected to follow.

    For infrastructure buyers, the significance is less about a single new vulnerability and more about the framing. Routers and firewalls that historically sat outside patch cycles and asset inventories are being reclassified, at least rhetorically, as first-class security assets. That has procurement, staffing and lifecycle implications for anyone running network gear at scale.

    The Edge Is the New Front Door

    For years, defenders concentrated on endpoints, identity and cloud workloads while edge devices — the routers, VPN concentrators and firewalls that sit between the internet and the internal network — were treated as appliances. State-linked operators noticed. Compromising an edge device gives an intruder a stable foothold with elevated network visibility, often below the level where endpoint detection tools can see. The current US warning is an acknowledgement that this asymmetry has become material at national scale.

    The economic pull for attackers is straightforward: one exploitable router can grant persistent access to every device behind it, and these devices are rarely rebooted, rarely re-imaged and often run firmware that has not been updated in years. That is a high-yield target for espionage groups that value durability over noise.

    What Router Hygiene Actually Means

    NSA’s guidance in this space typically covers a familiar but under-executed set of controls: keep firmware current, disable unused management services, restrict administrative access to trusted networks, replace default credentials, enable logging, and retire devices that no longer receive vendor patches. None of it is exotic. The gap the advisory is trying to close is operational, not conceptual — most organizations know the checklist and still do not run it end-to-end on their perimeter fleet.

    For smaller operators and home users, the practical implication is blunter: a consumer router that stopped getting firmware updates two years ago is a liability regardless of the brand on the box. The advisory implicitly pushes the market toward vendors that commit to defined support lifecycles, and away from cheap gear with unclear patch pipelines.

    Winners, Losers and Second-Order Effects

    Network vendors with mature secure-boot, signed-firmware and managed-update stories stand to benefit from any tightening of buyer expectations. Managed network and security service providers benefit too, because most organizations lack the staff to run a disciplined router hygiene program across dozens or hundreds of sites. The losers are end-of-life devices still in production and the budgets that have deferred their replacement.

    There are second-order effects worth flagging. Regulators and insurers tend to translate advisories like this into questions on audits and renewal forms; expect edge device patch status and end-of-support inventory to become recurring line items. Enforcement, however, is not automatic — a warning is not a rule, and the source coverage does not indicate any new binding requirement.

    Reading the Advisory Fairly

    It is worth being precise about what the source does and does not establish. The Cybersecurity Dive report describes a US government warning and NSA guidance; it is not, on its own, a technical disclosure of a specific new vulnerability chain, victim list or attribution to a named group. Readers should treat the advisory as a policy signal backed by prior public incidents rather than as a fresh indicator-of-compromise release.

    That framing cuts both ways. Skeptics who dismiss such warnings as vendor-friendly demand generation should note that the underlying pattern — state-linked targeting of network edge devices — has been documented repeatedly in prior US and allied advisories. Equally, industry claims that a given product line is inherently safer than another deserve the same scrutiny the advisory implicitly applies to unpatched fleets.

    Background

    US government agencies including the NSA and CISA have issued a running series of advisories over recent years warning that state-linked threat actors — attributed in prior public reporting to Russian, Chinese and other groups — target edge networking devices for espionage and pre-positioning. These campaigns exploit the fact that routers and firewalls are frequently unpatched, poorly monitored and long-lived compared with servers and endpoints.

    Router hygiene guidance from the NSA sits alongside broader ‘secure by design’ pressure on network vendors to ship devices with safer defaults, transparent patch pipelines and defined support lifecycles. The July 13, 2026 messaging reported by Cybersecurity Dive continues that trajectory rather than opening a new front.

    Source: US authorities warn that state-linked hackers are targeting vulnerable networking devices – Cybersecurity Dive — reporting on a US government advisory and accompanying NSA router hygiene guidance.

  • 8-Agency Tank Gauge Alert Shows Why AI Data Center Backup Fuel Is a Cyber Asset

    8-Agency Tank Gauge Alert Shows Why AI Data Center Backup Fuel Is a Cyber Asset

    TL;DR · 30-second read

    The Short Version

    Eight US government agencies, including the National Security Agency, warned on June 3 that hackers are breaking into the electronic gauges that measure what is inside fuel storage tanks, and tampering with them.

    These gauges sit on tanks across energy, chemical, farming and transport sites. The same kind of gauge often watches the diesel that keeps a data center’s emergency generators running during a power cut.

    If a gauge reports the wrong amount of fuel, a backup plan can fail exactly when it is needed. The agencies are urging every operator to lock these devices down.

    On June 3, 2026, the National Security Agency said in a press release that it had joined the Cybersecurity and Infrastructure Security Agency (CISA) and six other federal agencies in publishing a fact sheet titled CISA and Partners Urge Hardening Automatic Tank Gauge Systems. Automatic tank gauges (ATGs) are networked devices that remotely monitor fuel and liquid levels, temperature and potential leaks in storage tanks.

    The agencies said unattributed threat actors have been compromising internet-exposed ATGs and then modifying them through command execution. The co-authors are CISA, the NSA, the FBI, the Department of Energy, the Environmental Protection Agency, the TSA, the Department of Transportation and the Department of Agriculture. The NSA recommended that all operational technology owners in national security systems, the Department of War, the defense industrial base, the federal government and US critical infrastructure sectors review and implement the fact sheet’s mitigations.

    Executive Summary

    Eight federal agencies have jointly flagged ongoing malicious activity against a device most people have never heard of: the automatic tank gauge, the electronic sensor-and-console unit that reports how much liquid is in a tank, how warm it is and whether it is leaking. The warning names energy, chemical, food and agriculture, and transportation as affected sectors, and describes attackers not just reading these devices but changing them.

    For data center operators, the relevance is direct even though the sector is not singled out. Every facility with diesel backup generators stores fuel on site, and the number that tells an operator how many hours of emergency runtime remain is typically produced by tank-monitoring equipment of exactly this kind. A warning that such equipment is being actively modified by outsiders turns generator fuel data from a facilities housekeeping item into something that belongs inside the security program.

    The broader lesson is about scope. As AI campuses scale up their on-site generation and fuel storage, the attack surface grows with it, and much of that surface is operational technology (OT), the industrial control equipment that runs physical plant rather than business IT.

    The Gauge Behind the Runtime Promise

    A data center’s resilience story usually runs in layers: utility power, then batteries in the uninterruptible power supply (UPS) to bridge the first seconds of an outage, then diesel generators to carry the load for hours or days. That last layer is only as good as the fuel behind it, and operators state their emergency runtime in hours of on-site fuel. The figure they rely on comes from tank monitoring, the level, temperature and leak readings the agencies say ATGs are built to provide.

    The agencies describe attackers compromising internet-exposed ATGs and then modifying them through command execution, meaning they issued commands that changed how the device behaves. Applied to a generator fuel system, the operational risks are straightforward to reason about: a gauge that overstates fuel can leave an operator believing it has a day of runtime when it has far less; one with suppressed leak alarms can let a spill go unnoticed; one that throws false alarms can trigger unnecessary emergency deliveries or shutdown procedures. None of those outcomes needs an attacker to touch the generator itself. The fuel reading is part of the power chain, and that is why it now has to be defended like one.

    That argument scales with AI. Large AI training and inference campuses draw far more power than traditional enterprise halls, and operators that back that load with diesel need correspondingly more generators and more stored fuel. More tanks mean more gauges, and every networked gauge is a device that has to be inventoried, patched or isolated.

    A Broad Coalition, a Broader Recommendation

    The makeup of the coalition says something about how the agencies view the problem. The EPA regulates fuel storage and leak detection, the Department of Energy covers the energy sector, the TSA and Department of Transportation cover pipelines and transport, and the Department of Agriculture covers farm fuel storage. Pairing them with the NSA, CISA and the FBI signals that the concern spans environmental, safety and national security lines at once.

    Data centers are not among the sectors the fact sheet names. But the NSA’s recommendation is deliberately wide: all OT owners and operators in national security systems, the Department of War, the defense industrial base, the federal government and US critical infrastructure. Facilities that host government workloads, defense contractors or critical services fall squarely inside that language, and colocation providers serving those customers will likely be asked about it.

    Where Security Programs Tend to Thin Out

    Tank gauges often sit in an organizational gap. They are frequently specified by the fuel system or generator contractor, maintained by facilities staff, and sometimes connected so that a fuel supplier or monitoring service can read them remotely. The network team may not know they exist, and the security team may never have scanned them. That is the pattern that leaves OT devices reachable from the internet, and it is the exposure the agencies describe.

    The practical response is unglamorous: find every gauge, confirm none is reachable from the public internet, place them behind segmented networks, review remote-access arrangements with vendors, and apply the fact sheet’s mitigations. Just as important, operators should keep an independent way to verify fuel levels, such as periodic manual measurement, so that a single compromised device cannot quietly rewrite the runtime assumption an entire backup plan depends on.

    The agencies have not attributed the activity, and the warning should be read for what it is: evidence of ongoing compromise and modification of exposed devices, not a claim that any data center has lost backup power. That measured reading is still enough to justify action, because the fix is cheap relative to the consequence.

    Background

    Automatic tank gauges have been standard equipment on fuel storage tanks for decades, in large part because they automate the leak detection that environmental rules require for stored fuel. Over time many gained network interfaces so that owners, fuel suppliers and service contractors could read them remotely, and security researchers have documented internet-reachable units for roughly a decade.

    CISA leads federal efforts to protect US critical infrastructure and frequently co-publishes guidance with the NSA, the FBI and sector-specific agencies. Data centers depend on the same class of equipment: diesel generators backed by on-site fuel tanks remain the dominant form of emergency power, and fuel monitoring is part of how operators plan how long they can run without the grid.

    Sources

    Source: NSA Joins CISA and Partners to Release Guidance on Hardening Automatic Tank Gauge Systems, the NSA’s June 3, 2026 announcement of a joint eight-agency fact sheet on malicious activity targeting internet-exposed ATG systems.

  • NSA and Allies Issue First Joint Guidance on Securing Agentic AI Systems

    NSA and Allies Issue First Joint Guidance on Securing Agentic AI Systems

    The U.S. National Security Agency (NSA) has joined the Australian Signals Directorate’s Australian Cyber Security Centre (ASD’s ACSC) and other partner agencies to release joint guidance on agentic artificial intelligence systems — AI that doesn’t just answer questions but autonomously plans and executes tasks. Announced April 29, 2026, it is the first major multi-government security framework aimed specifically at AI agents, arguably the fastest-growing new attack surface in enterprise technology.

    Executive Summary

    According to the announcement, the NSA — alongside ASD’s ACSC and other unnamed partner agencies — has published guidance on agentic AI systems: software built on large language models that can take actions on a user’s behalf, such as browsing, writing code, calling APIs, or operating other software. That autonomy is precisely what makes agents useful, and precisely what makes them dangerous when compromised: an attacker who subverts an agent inherits everything the agent is allowed to do.

    The release matters less for any single recommendation than for what it signals. When signals-intelligence agencies from multiple allied nations co-sign a document about a technology category, that category has crossed a threshold — from experimental tooling to infrastructure that governments believe adversaries are actively probing. Enterprises deploying AI agents now have an authoritative reference point, and vendors selling them have a bar to be measured against.

    Autonomy Changes the Threat Model

    A conventional chatbot that gets manipulated produces bad text. An agentic system that gets manipulated produces bad actions — because agents are wired to tools, credentials, file systems, and APIs. The security community has spent two years documenting how techniques like prompt injection (hiding malicious instructions in content an AI reads, such as a webpage or email) can redirect an agent’s behavior. When the agent can send messages, move money, or modify infrastructure, a manipulated input stops being an embarrassment and becomes the equivalent of a compromised employee account.

    That is why agentic AI merits its own guidance rather than a footnote to existing AI security advice. Earlier frameworks focused on securing models, training data, and deployment pipelines. Agents add a different problem: the model’s outputs are now inputs to real systems, so classic security disciplines — least privilege, sandboxing, audit logging, human approval for consequential actions — must be rebuilt around a component that behaves probabilistically rather than deterministically.

    The Allied Playbook: Guidance Before Regulation

    This release fits a well-established pattern. The NSA, ASD’s ACSC, and partners including the UK’s NCSC and the U.S. CISA have jointly published a sequence of AI security documents since late 2023 — guidelines for secure AI development, for deploying AI systems securely, and for AI data security. Each followed the same model: non-binding, principles-based guidance issued jointly so that multinational enterprises face one aligned reference instead of a patchwork.

    Non-binding does not mean toothless. In practice, joint government guidance tends to become a de facto procurement standard — government buyers cite it in contracts, insurers and auditors reference it, and regulators later treat it as evidence of what “reasonable” security looked like at the time. Vendors of agent platforms and the enterprises deploying them should read this release as an early draft of tomorrow’s compliance expectations, arriving while the market is still young enough to adapt cheaply.

    What It Means for Enterprise and Infrastructure Operators

    For organizations already piloting AI agents, the immediate implication is organizational: agent deployments now belong in the security team’s scope, not just the innovation team’s. That means treating agents as privileged identities — with scoped credentials, network segmentation, activity logging, and defined blast radius — rather than as features of a productivity suite. Buyers evaluating agent platforms gain a useful question set: how does the vendor constrain what the agent can do, log what it did, and contain it when it misbehaves?

    For infrastructure providers — data centers, cloud and connectivity operators — agentic AI is both a workload to host and a tool their customers will point at their own environments. Isolation, observability, and identity infrastructure become selling points as enterprises look for places to run agents with enforceable boundaries. Government attention at this level tends to accelerate, not chill, enterprise adoption: clear security expectations reduce the uncertainty that keeps cautious industries on the sidelines.

    Background

    Governments began issuing coordinated AI security guidance almost as soon as generative AI reached enterprises: allied agencies including the NSA, CISA, the UK’s NCSC, and ASD’s ACSC jointly published guidelines for secure AI system development in November 2023, guidance on deploying AI systems securely in April 2024, and AI data security guidance in 2025. The NSA’s Artificial Intelligence Security Center, created in 2023, has anchored the U.S. side of that effort.

    Over the same period, the industry’s center of gravity shifted from chatbots to agents — AI that can use tools, browse, code, and act with limited supervision — driven by rapid capability gains in frontier models. Security researchers flagged early that autonomy plus tool access creates a fundamentally new attack surface; this April 2026 release is the first time that concern has been addressed head-on at the multi-government level.

    Source: NSA joins the ASD’s ACSC and Others to Release Guidance on Agentic Artificial Intelligence Systems — National Security Agency announcement of joint international guidance on securing agentic AI, published April 29, 2026.