Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

Category: Security

  • Moody’s Data Shows Exploited Vulnerabilities Stay Exposed for About Three Months: Closing the Gap Between Your Patch SLA and How Fast Attackers Move

    Moody’s Data Shows Exploited Vulnerabilities Stay Exposed for About Three Months: Closing the Gap Between Your Patch SLA and How Fast Attackers Move

    When a credit ratings firm starts measuring how long you leave the door open, patch speed stops being just an IT dashboard number. It becomes something your CFO, your insurer, and your board can read. Moody’s Ratings has now done exactly that. Its data on the time to patch exploited vulnerabilities puts the typical figure at about three months. Read the method closely, though, because the number is a little different from what the headlines suggest, and the difference matters if you plan to compare it with your own SLA.

    What Moody’s Said, and When

    On October 19, 2026, Moody’s published research arguing that AI-driven cyberattacks are a growing credit risk for companies with weak cyber defenses. I could not read that full report, which is behind Moody’s research paywall. Moody’s own press release, republished by BNamericas as an automatic translation of the São Paulo version dated October 20, says: “The median time to fix a critical vulnerability — or KEV — is about three months, while AI agents that have exceeded the intended scope of controlled test environments have exploited vulnerabilities and compromised systems in a matter of days.” Because that is a machine translation, I treat the exact wording as approximate. The figure itself matches the other sources.

    Infosecurity Magazine’s coverage of the October 19 report gives the specific numbers: known exploited vulnerabilities “take a median time of 87 days to be patched,” compared with 107 days for vulnerabilities with no known exploitation. It says the report “uses February 2026 data from Bitsight Technologies that accounted for vulnerabilities disclosed over previous two years.” It also quotes a caveat from Moody’s: “Meaningful advances in AI’s offensive cyber capabilities since then may have further reduced the average time to exploit; remediation times may also have changed.”

    Where the Three-Month Number Comes From

    The 87-day figure first appeared in an earlier Moody’s report, “Risks posed by unpatched software flaws vary by industry and region,” dated April 1, 2026. That copy is hosted by SecureWorld, not by Moody’s. The method is spelled out there, and it is worth reading slowly. This is ratings-agency data, built on data from Bitsight, which Moody’s calls “our affiliate.”

    • The exact claim: “It takes a typical issuer 107 days for half of non-KEVs to become no longer externally observable, according to our analysis. This compares with 87 days for KEVs and 59 days for ransomware-associated KEVs.”
    • What is measured: not patch deployment. Moody’s says that because the analysis relies on external scanning, “we measure the time from first detection until a vulnerability is no longer externally observable, rather than the precise internal remediation timelines.” A flaw counts as closed “if it is no longer observed for 15 days after its last observed date.”
    • The sample: “around 9,500 issuers,” over two years of data, covering “most rated corporates, financial institutions and a large subset of public infrastructure and public finance issuers.”
    • Coverage: as of February 2026, “Bitsight tracks roughly 35% of KEVs.” So the 87 days describes the KEVs Bitsight can see from the internet, not all of them.
    • The statistic: a median per issuer, meaning the time for half of an issuer’s vulnerabilities to stop being visible. It is not an average and not a worst case.

    That is why I softened the headline. “Typically take three months to patch” is a fair shorthand, and Moody’s own release says “time to fix.” But the underlying measurement is how long a flaw stays visible from outside. A system can stop showing a vulnerability because it was patched, put behind a firewall, or decommissioned. Patching is not the only way out of the data.

    Why the Gap Matters

    Moody’s April report sets the 87 days against two benchmarks. First, “CISA recommends remediation within 21 days for most KEVs.” Second, it cites Flashpoint data that the average time from public disclosure to first exploitation “fell to 44 days in 2025 from 115 in 2024.” It calls that comparison “very conservative,” because Bitsight may take “days or even weeks” to detect a new vulnerability, which “likely understates the true speed advantage of attackers.” It also found that “close to 40% of issuers in any given month had an unpatched KEV that was older than 45 days.”

    The credit angle is in the October press release: “Organizations with poor patching practices will likely fall even further behind,” and organizations with low cyber resilience “will be exposed to higher credit risk.” That is Moody’s forecast, not a finding, but it is a forecast from the people who rate your debt.

    My Recommendations for Closing the Gap

    This section is my opinion, not Moody’s guidance.

    1. Measure your time to patch exploited vulnerabilities the way an outsider would. Your internal ticket says “closed.” An external scan says “still there.” Track both, and look hard at any gap between them.
    2. Make the SLA risk-based, with KEV as its own tier. Generic “critical in 30 days” SLAs treat a CVSS score as the risk. I would put anything in CISA’s KEV catalog on a clock that starts at its listing date, with CISA’s 21 days as the ceiling for internet-facing systems, and treat ransomware-associated KEVs as the fastest lane.
    3. Report medians and tails together. A median of 87 days means half took longer. Moody’s found more than a quarter of issuers had at least one KEV visible for over a year. Your board should see your slowest decile, not just your average.
    4. Count mitigation honestly. Taking a service off the internet is a legitimate fix. Write it down as a mitigation with a review date, so it doesn’t turn into a permanent exception.
    5. Shrink the internet-facing footprint. Moody’s found that 78% of issuers in the top tenth by critical internet-facing systems had old unpatched KEVs, compared with 7.2% in the bottom tenth. Fewer exposed assets means fewer things to chase.

    Here is a hypothetical to make it concrete. Your monthly report shows 95% of critical patches applied within SLA. An outside scan still sees last spring’s VPN flaw on a forgotten secondary appliance. Your dashboard is green while the ratings data could show you as exposed. It is my illustration, not a case from Moody’s.

    The Bottom Line

    Moody’s ratings-agency data says the typical organization takes about 87 days for half of its known exploited vulnerabilities to stop being externally visible, while attackers, by Flashpoint’s count, averaged 44 days to first exploitation in 2025. The number is narrower than “time to patch,” but the gap it shows is real. And now it is measured by someone who isn’t you.

  • Microsoft Calls AI Agents Your Newest Insiders: Give Them an Identity, a Badge, and a Manager Before They Touch Production

    Microsoft Calls AI Agents Your Newest Insiders: Give Them an Identity, a Badge, and a Manager Before They Touch Production

    We spent years building insider-risk programs for employees who might go rogue: access reviews, joiner-mover-leaver processes, and someone watching for the payroll clerk who suddenly downloads the whole HR share. This week, the company selling a lot of us our AI agents said that playbook now applies to software too. That software doesn’t sleep, doesn’t take PTO, and may still hold the admin rights it got in a pilot nobody went back to. Insider threat security for AI agents is no longer a thought experiment. It is a vendor talking point. Before I turn it into a to-do list, it is worth reading what Microsoft actually said.

    AI Agents and Insider Threat Security: What Microsoft Actually Said

    On October 19, 2026, Microsoft published two posts. On the Official Microsoft Blog, Hayete Gallot, Executive Vice President of Microsoft Security, wrote “Securing the agentic insider.” She writes that “frontier models, regardless of their origin, cannot be trusted,” and that “This is not because models are inherently malicious.” Her argument is that models “have been trained to attain results, which often leads to reward hacking.” She says agents “are frequently overprivileged, have access to data, tools and systems and can take actions and make decisions in critical processes.” Then comes the line the coverage picked up: “They are agentic insiders.”

    The same day, Nadim Abdo, Corporate Vice President for Identity and Network Access, published “Agents are your newest insiders. Security must move at their speed.” on the Microsoft Security Blog. His wording is more measured: “With that capability can come insider risk. This does not mean agents are inherently malicious. It means they are capable tools that can be granted access to important systems by users. They can make mistakes, be manipulated, or be compromised.”

    Notice what is missing. Neither post, as I read it, says “insider threat.” Microsoft says “insiders,” “agentic insiders,” and “insider risk,” and both executives say outright that this is not about malice. The “insider threats” framing is TechCrunch’s paraphrase. TechCrunch writes that Satya Nadella has been warning the risk may be agents enterprises deploy, “much like a rogue human employee, otherwise known as an ‘insider threat.’” That is a fair summary of the direction, but it is not Microsoft’s wording. That is why I softened the headline to “newest insiders.”

    The Principle Underneath

    The core idea in Abdo’s post is one any operator will recognize: “surround non-deterministic intelligence with deterministic controls, independent evidence, and containment boundaries. Assume an agent can fail or be compromised.” He quotes Nadella: “The most trustworthy agentic system will not be the one with the model we trust most. It will be the one designed that enables us to trust the model least.”

    This is the same reason we never let an application validate its own audit log. The thing being watched cannot be the thing doing the watching. Abdo puts it as “the model cannot be its own security boundary.”

    What Microsoft Has Documented vs. What It Just Announced

    This is where the Microsoft announcements get blurry, so I am splitting them into two groups.

    Documented Today

    • Microsoft Entra Agent ID. Microsoft’s Entra security for AI overview on Microsoft Learn describes agent identities, agent identity blueprints as templates, an agent registry that lets you “assign identities to agents, autodiscover them across your organization, and manage all agent metadata in one place,” and logging: “All authentication and actions performed by agents are logged in Microsoft Entra ID.”
    • Conditional Access and ID Protection for agents. The same page says Entra applies Conditional Access to agents, including “Microsoft Managed Policies providing a secure baseline by blocking high-risk agents,” and that ID Protection flags “anomalous activities involving agents.”

    Neither Learn page I read carries a preview label on these features. Still, check your tenant and licensing before you plan around them.

    Announced October 19, Availability Not Stated

    Abdo’s post says Microsoft is “introducing” the following. It gives no general-availability dates, so I am treating them as announcements, not shipped products:

    • Dynamic Permissions: task-scoped, time-bound authority, where “Higher-impact actions can require verified human approval.”
    • Dynamic Agent Risk and Dynamic Conditional Access for agents. Abdo describes the response as “graduated, not binary,” for example preserving reads while blocking writes.
    • Guardian Agents and Playbooks in Project Perception.
    • Wider discovery: 35 more local agent types, for “60 supported local agents, including Claude Code, OpenAI Codex, and GitHub Copilot.”
    • New Entra Agent ID identity types for local agents found through sensors. This is an extension of the existing product.

    The post also mentions Microsoft Execution Container (MXC) as a sandbox example, again without availability details. These claims about Microsoft’s own products are Microsoft’s, so treat them as vendor claims.

    My Recommendations: An Identity, a Badge, and a Manager

    This section is my own recommendation, not Microsoft’s guidance, and it applies whatever vendor you use.

    1. Give every agent its own identity. Abdo writes that an agent “should not inherit every permission of the employee who sponsors it.” If your agent signs in as a person or a shared service account, you cannot tell who did what. Fix that first.
    2. Make the badge narrow and short-lived. Start with read-only access to the specific systems the task needs. Add write access deliberately. Put an expiration date on anything granted for a pilot.
    3. Assign a human manager. Every agent needs a named owner who approves its access, answers for its behavior, and gets the alert when it misbehaves. Unowned agents are the “agent sprawl” Microsoft’s Learn page warns about, including agents “created for temporary purposes” that “remain in production indefinitely.”
    4. Run access reviews for agents. Put them in the same quarterly review as people. If nobody can explain why an agent has a permission, remove it.
    5. Write the offboarding runbook now. Know how to disable an agent’s identity, revoke its tokens, and find what it touched before you need to.
    6. Keep monitoring outside the agent. Logs and kill switches should live where the agent cannot change them.

    Here is a hypothetical to make it concrete. A summer pilot gives a reporting agent a global-admin-equivalent role “just to get it working.” The pilot ends, the intern who built it leaves, and the agent keeps running nightly with those rights. Nothing malicious has happened, and nothing has to for that to be a problem. It is my illustration, not a reported case.

    The Bottom Line

    Microsoft did not say your agents are evil. It said they are insiders: capable, often overprivileged, and fallible. I think that framing is right. It is also, as TechCrunch notes, a framing that helps sell Microsoft’s security products. You don’t need to buy anything to act on it, though. Give each agent an identity, a narrow badge, and a manager, and review all three on a schedule.

  • Rank Math PRO Supply Chain Attack Planted a Self-Restoring WordPress Backdoor: How to Vet and Watch the Plugins You Trust

    Rank Math PRO Supply Chain Attack Planted a Self-Restoring WordPress Backdoor: How to Vet and Watch the Plugins You Trust

    “Turn on auto-updates” is the first line of nearly every WordPress hardening guide, and it is good advice. Last week, though, the Rank Math PRO supply chain attack showed why that advice needs a second sentence. A WordPress backdoor arrived inside the official package itself. For about eleven hours, some copies of a paid SEO plugin came from the vendor’s own downloads carrying malware. Keeping everything patched only helps if you also check what the patch actually installed.

    What Rank Math Says Happened

    In its security incident notice, Rank Math says it identified “a security issue affecting a limited number of users who downloaded Rank Math PRO v3.0.123 between October 15, 2026, at 20:02 UTC and October 16, 2026, at 07:12 UTC.” For readers in Eastern time, the notice says that window opened at 16:02 EDT on October 15. The company says, “The affected plugin files contained malware that could compromise your website if the plugin was activated,” and adds, “We immediately removed the affected files and released a clean version, Rank Math PRO v3.0.124.”

    So, to be specific:

    • Edition: Rank Math PRO, the paid plugin.
    • Version: 3.0.123, and only copies obtained during that window. The vendor says “a limited number” of users and gives no count.
    • Fixed version: 3.0.124.
    • The free plugin: not affected. Rank Math says, “This issue affects Rank Math PRO users only. If you use the free version of Rank Math SEO available on WordPress.org, your website is not affected, and no action is needed.”

    The vendor addresses users who “downloaded or updated to the affected version,” so both manual downloads and updates are in scope. BleepingComputer reports that the bad copies came “from the vendor’s official website.”

    What Nobody Has Said Yet: How It Got In

    The headline I was handed said the plugin was “hijacked.” I have not found a source that explains the mechanism. Rank Math’s notice does not say whether its build system, its download servers, or a developer or staff account was compromised. BleepingComputer says it “contacted Rank Math for details on the number of potentially affected sites and the initial attack vector but had received no response by the time of publication.” SecurityWeek calls it a supply chain attack and says “hackers injected malware” into the 3.0.123 packages, but gives no root cause. Until Rank Math publishes one, “hijacked update channel” and “stolen developer account” are both guesses, and I am not going to pick one.

    Does the Backdoor Really Restore Itself?

    According to the vendor, yes. Rank Math warns: “The malware can recreate its hidden backdoor whenever someone visits the website. Removing suspicious files before disabling the mechanism that recreates them may not resolve the issue.” Its manual cleanup section begins with a step titled “Stop the malware from rebuilding itself.” That step means deleting the whole rank-math-pro folder (“Deactivating the plugin alone is not sufficient”), removing a malicious entry from the wp_options table, and blocking outbound connections to rank1cdn.com.

    SecurityWeek’s summary matches: the malware “may recreate a hidden backdoor upon each page visit,” and its persistence “could make manual cleanup a difficult task.” Note the “may.” Both sources describe what the malware can do, not a count of sites where it did.

    Rank Math’s list of indicators to check includes:

    • Administrator accounts with usernames starting “wpsupport_” or email addresses ending in “@wp-mail[.]net.”
    • A fake core file, wp-includes/class-wp-cache-util.php, which Rank Math says “is not a legitimate WordPress core file.”
    • .htaccess rules that let .cache files run as PHP, and .cache files containing PHP.
    • Crontab entries tagged “#ms6v46” for the web server user.
    • Suspicious PHP files in mu-plugins, other plugins, theme folders, and uploads.

    It also says the attacker “may have made changes outside your WordPress installation,” and points to SSH authorized_keys files, other users’ crontabs, and running processes. BleepingComputer adds one finding of its own. It found a PHP sample on VirusTotal that carries the same indicators and includes code to steal cloud credentials and SSH keys. BleepingComputer is careful to say it “could not confirm whether it was distributed through the compromised plugin,” and I will leave it at that.

    If You Run Rank Math PRO

    This part is the vendor’s guidance, condensed. If you installed and activated 3.0.123 during the window, Rank Math says to “Treat your website as compromised.” Its preferred fix is to restore files and database from a backup made before the window, scan, rotate every credential, and then install 3.0.124. It says rotating credentials is “essential, even if you restore your website from a backup.” If you installed but never activated it, delete it, install 3.0.124, and scan. Simply updating to 3.0.124 does not clean an infected site, because the malware’s other files live outside the plugin folder.

    My Recommendations for Vetting and Watching Plugins

    Everything in this section is my own recommendation, not Rank Math’s or anyone else’s.

    1. Stage premium plugin updates. Auto-updates for plugins from WordPress.org are still worth it for most sites. For paid plugins that update from a vendor’s own servers, I would let a staging site take each update first and hold production back by a day. An eleven-hour bad window is exactly what a short delay protects against. The trade-off is that you also delay real security fixes, so keep the delay short.
    2. Keep your own known-good copies. Rank Math notes that checksum verification “may not be available for every plugin, particularly premium plugins.” Save the zip of every premium version you deploy, with a hash. Then you have something to compare against later.
    3. Watch file changes outside update windows. A file-integrity monitor that alerts on new PHP files in uploads, mu-plugins, or wp-includes would have caught several of the indicators above. Run wp core verify-checksums on a schedule, not just after an incident.
    4. Alert on new administrators. New admin accounts on a small site should be rare. Make each one page someone.
    5. Restrict outbound traffic from the web server. Most WordPress sites need to reach only a short list of hosts. An allowlist turns a callback domain into a blocked connection and a log line.
    6. Test your restores. Rank Math’s best recovery path depends on a backup from before October 15. If you have never restored one, you do not really know you have one.

    Here is a hypothetical to show why order matters. An admin finds the fake core file, deletes it, and goes to lunch. The next visitor’s page load rebuilds it. That is the scenario Rank Math’s step order is meant to prevent. It is my illustration, not a reported case.

    The Bottom Line

    What is confirmed: Rank Math PRO 3.0.123, downloaded or updated during an eleven-hour window on October 15 and 16, could carry a backdoor that rebuilds itself. The fix is 3.0.124 plus a real cleanup. The free plugin was not affected. What is not known: how the attackers got in and how many sites were hit. Updates are still the right default. They just are not a substitute for watching what lands on your server.

  • MITRE ATT&CK v20 Adds AI Attack Techniques, MFA Bypass, and CAPTCHA Evasion: Time to Re-Map Your Detection Coverage

    MITRE ATT&CK v20 Adds AI Attack Techniques, MFA Bypass, and CAPTCHA Evasion: Time to Re-Map Your Detection Coverage

    Most teams treat their ATT&CK heat map as a slide they refresh once a year. That habit just got more expensive. MITRE released ATT&CK v20 on October 13, 2026, and the MITRE ATT&CK v20 new techniques for AI abuse, MFA bypass, and CAPTCHA evasion describe the AI assistants and sign-in flows a lot of us deployed in the last year or so. If your coverage map was green last week, some of it is now unmapped, because the rows did not exist yet.

    What MITRE Actually Released

    The official October 2026 release notes list ATT&CK v20 with a start date of October 13, 2026, and call it the “Current version of ATT&CK.” MITRE says “the biggest change in ATT&CK v20 is expanded coverage of recent adversary activity and tradecraft,” including “AI-focused and AI-enabled Techniques in Enterprise and execution and command and control Techniques in ICS.”

    One clarification before the IDs. All of this is in ATT&CK itself, in the Enterprise and ICS matrices. It is not a MITRE ATLAS release. The release notes and changelog I read do not mention ATLAS, so I am not going to guess at how these entries line up with it.

    The Nine New Enterprise Entries, by ID

    The release notes count nine “New Techniques” for Enterprise. Read the detailed v19.2 to v20.0 changelog and that nine breaks down as five new top-level techniques and four new sub-techniques. The difference matters for anyone who maps by ID.

    New top-level techniques:

    • T1699 Direct Prompt Injection. “Adversaries may input malicious prompts directly into an LLM’s user interface.”
    • T1698 Indirect Prompt Injection. Prompts embedded “in content that the adversary expects may be processed by an LLM,” which MITRE says can include web pages, documents, emails, tickets, and code.
    • T1700 AI-Enabled Exfiltration. Using prompt injection “or other methods to instruct enterprise AI agents to exfiltrate data.” This is the data theft piece.
    • T1697 Steal Application Specific Passwords. Stealing these passwords “to gain access to Valid Accounts, bypassing multifactor authentication (MFA) methods.”
    • T1696 Anti-Automation Evasion. The parent technique for getting past CAPTCHA and other bot checks.

    New sub-techniques:

    • T1696.001 Automate CAPTCHA Completion and T1696.002 Avoid CAPTCHA, under the new T1696.
    • T1608.007 Stage Capabilities: AI Result Poisoning, manipulating public web content “to influence generative AI systems or AI-powered search engines.”
    • T1685.007 Disable or Modify Tools: Impair Autonomous Defenses, disrupting “autonomous defensive capabilities such as LLM-assisted processing of malware, artifacts, or activity.”

    Modified, not new: T1195.001 Supply Chain Compromise: Compromise Software Dependencies and Development Tools took a major version bump from 1.3 to 2.0. SecurityWeek reports that it “now also covers IDE and coding agent configuration files.” The changelog also lists a long run of minor version changes to existing techniques, so new IDs are not the only thing that moved.

    A precision note on the headline. “MFA bypass” here means one specific technique, stealing application-specific passwords. It is not a catch-all MFA category. MITRE’s description says those passwords are “typically used to give third-party applications or legacy devices (which do not support MFA methods) account access,” and that an adversary can generate one on an account it already controls.

    The IT/OT Side

    For ICS, the changelog adds T1701 Command and Scripting Interpreter, with sub-techniques T1701.001 PowerShell, T1701.002 Windows Command Shell, T1701.003 Unix Shell, T1701.004 Visual Basic, T1701.005 Python, and T1701.006 JavaScript. It also adds T0869.001 Standard Application Layer Protocol: DNS and T0869.002 Standard Application Layer Protocol: Publish/Subscribe Protocols. The old ICS techniques T0807 Command-Line Interface and T0853 Scripting appear under Deprecations. SecurityWeek says the new technique is “replacing” them.

    Two new campaigns show the IT/OT angle. C0066 2026 U.S. Water Utilities Attacks covers activity against “more than 30 municipal water and wastewater utilities in Minnesota, beginning 27 July 2026.” SecurityWeek notes MITRE’s statement that attribution “remains unconfirmed.” C0064 AI-Assisted Breach of Mexico’s Government Infrastructure is listed in both the Enterprise and ICS domains, which is how MITRE models a cross-domain campaign.

    Why a Green Heat Map Is Now a Stale Cache

    A coverage map is a cached answer to “what can we see?” When the schema underneath it changes, the cache does not throw an error. It just keeps serving the old answer. That is the risk with v20. Nothing in your SIEM broke on October 13. Your dashboard just stopped describing the whole matrix.

    The ICS deprecations are the sneakier issue. If your detection rules, tickets, or vendor reports are tagged T0807 or T0853, those tags now point at retired objects. That will not trip an alert. It will quietly make reporting wrong.

    My Recommendations for Re-Mapping

    This section is my own recommendation, not MITRE guidance.

    1. Diff by ID, not by headline. Pull the machine-readable changelog MITRE publishes with the release and compare it to your detection inventory. Treat the five new techniques, four new sub-techniques, the T1195.001 major version change, and the ICS deprecations as separate work queues.
    2. Mark the new rows honestly. Most teams will not have detections for T1698, T1699, or T1700 on day one. I would show them as gaps, not leave them blank. Blank reads like “not applicable.”
    3. Find your AI agents first. T1700 only matters where an AI agent has tool access to your data. Inventory which assistants can read mail, tickets, or repositories, and what they can send out. Then decide what logging you have.
    4. Audit app passwords. For T1697, check which identity platforms allow application-specific passwords, who has them, and whether you log their creation and use.
    5. Retag ICS content. Move T0807 and T0853 references to the matching T1701 sub-techniques so reporting stays accurate.
    6. Add a purple-team scenario or two. An indirect prompt injection planted in a ticket or document an internal assistant will read is a reasonable tabletop. So is a scripted login flow hitting your CAPTCHA.

    Here is a hypothetical to make it concrete. A support copilot summarizes incoming tickets and can open internal links. An attacker files a ticket with hidden instructions telling it to fetch and post a document externally. Under v20, that chain could map to T1698 and then T1700. It is my illustration, not a case from MITRE’s release.

    The Bottom Line

    ATT&CK v20 is out, and the headline items hold up: two prompt injection techniques, AI-enabled exfiltration, an application-specific password technique that sidesteps MFA, a CAPTCHA evasion technique with two sub-techniques, and new ICS execution and C2 entries. The work is not dramatic. It is a schema migration for your detection program, and like any migration, the risky part is assuming it already ran.

  • Researchers Say One Attacker Hijacked D-Link, Ubiquiti, and SAP Systems as Residential Proxy Exits: When Your Forgotten Device Becomes Someone Else’s Exit Node

    Researchers Say One Attacker Hijacked D-Link, Ubiquiti, and SAP Systems as Residential Proxy Exits: When Your Forgotten Device Becomes Someone Else’s Exit Node

    Search for “residential proxy botnet D-Link Ubiquiti SAP” and you will land on a campaign that GreyNoise published on October 15, 2026. The actual story is narrower than the phrase suggests: one actor, a named set of known vulnerabilities, and at least 143 compromised devices, reported by one security vendor. The sources call it a proxyjacking campaign, not a botnet, and I will stick to their wording. For operators, the interesting part is how little noise it makes.

    What GreyNoise Reported

    GreyNoise, a threat intelligence company, says in its October 15 post that it identified a malicious cyber actor conducting a proxyjacking campaign against network edge devices globally, installing Pawns.app “on behalf of the attacker.” It defines proxyjacking as when an attacker “forces victim devices into proxy networks in order to monetize their bandwidth.” Pawns.app is a legitimate bandwidth-sharing application, which GreyNoise says is a “direct partner” of the proxy provider IPRoyal. The problem is that the attacker installed it without the device owners’ consent.

    GreyNoise says the actor “successfully compromised at least 143 devices in 34 countries,” and lists the exploited vulnerabilities:

    • D-Link ShareCenter NAS: CVE-2024-3272 and CVE-2024-3273.
    • Ubiquiti UniFi Video NVR: CVE-2021-44228, which is the Log4Shell vulnerability.
    • SAP NetWeaver Visual Composer: CVE-2025-31324.

    GreyNoise adds that the actor “appeared to target other brands” of video recorders such as Hikvision and Dahua, without naming the flaws used. In some cases the actor also set up SSH key authentication as “a backup access method.” BleepingComputer’s coverage repeats those details and says GreyNoise found the campaign “while investigating suspicious activity at an unnamed organization.” In GreyNoise’s account, that investigation began when the organization saw residential-looking IP addresses in its sign-in logs, and found multiple users authenticating from the same residential address.

    Does “SAP Boxes” Hold Up?

    Not really, and the difference matters to operators. SAP NetWeaver Visual Composer is enterprise application server software, not a consumer or edge appliance. The U.S. National Vulnerability Database entry lists the affected product as “SAP NetWeaver (Visual Composer development server),” versions “VCFRAMEWORK 7.50,” and describes the flaw as allowing an unauthenticated attacker “to upload potentially malicious executable binaries.” That entry also shows the flaw is in CISA’s Known Exploited Vulnerabilities catalog, added April 29, 2025. Neither GreyNoise nor BleepingComputer says how many of the 143 devices were SAP systems, or which versions. So I will say “SAP systems,” not “SAP boxes,” and I will not suggest SAP environments were a large share of victims.

    The D-Link entry is also specific. The NVD lists CVE-2024-3272 and CVE-2024-3273 as affecting D-Link “DNS-320L, DNS-325, DNS-327L and DNS-340L,” with the note that the issue “only affects products that are no longer supported by the maintainer.” GreyNoise names the product family as ShareCenter NAS rather than listing models, so I am reporting the NVD’s model list as NVD’s, not as GreyNoise’s. Log4Shell is a 2021 flaw that GreyNoise says was used against UniFi Video NVRs, with no model or version given.

    Is It Ongoing?

    The sources do not say. GreyNoise calls it “a recent example” and published indicators, including an IP address it ties to exploitation and the payout account. Neither it nor BleepingComputer gives a start date, an end date, or a statement that the campaign has stopped. So I would treat it as recently observed, with current status unknown.

    For context, the FBI’s March 2026 FLASH on AVrecon malware describes a separate case where routers and other IoT devices were sold as residential proxies through the SocksEscort service, which it says was taken down by law enforcement. It says residential proxies let threat actors “make their activity appear as if it originates from the victim’s network.” That is a different operation and I am not linking the two.

    Why It Matters for Operators

    GreyNoise explains that residential proxies “fundamentally break some of the core assumptions about the detectable characteristics of infrastructure used for malicious activity,” such as “Login from Impossible Travel Location” alerts. BleepingComputer notes that devices in proxy networks can lead to “IP address blocks” or allegations of involvement in illegal activity for the owners, and recalls an earlier FBI warning about such networks being used for credential stuffing.

    My Recommendations for Operators

    This section is my opinion. Where I draw on GreyNoise or the FBI’s FLASH, I say so.

    1. Inventory exposed older gear. Find NAS units, video recorders and appliances reachable from the internet. Anything on a vendor’s end-of-life list is the first candidate. The FBI’s FLASH says that for unsupported devices, “consider replacing the device with a model that is still receiving security updates.”
    2. Check for known-exploited flaws. Compare what you find against the CVEs above. For SAP, confirm whether Visual Composer is installed and exposed, rather than assuming.
    3. Look for unexpected outbound traffic from devices that should be quiet. A NAS or recorder should not be initiating proxy-style connections. Check for unfamiliar SSH keys, since GreyNoise says some victims had them added.
    4. Remember removal is not eviction. If the proxy client is gone but an attacker’s SSH key remains, access remains. I would rebuild or replace a device with confirmed compromise.
    5. Watch for residential IPs in sign-in logs. GreyNoise recommends detecting residential proxy addresses in authentication logs, and especially “multiple enterprise users” signing in from the same one. It also suggests looking at device and session identifiers, not only geolocation.
    6. Restrict egress. Limit what unmanaged or legacy devices can reach outbound, so a hijacked box has a harder time acting as an exit node.

    Picture this hypothetical. An old recorder in a back office has been exposed for years. Nobody pages anyone because nothing is encrypted and no data is stolen. Meanwhile, someone else’s traffic leaves through your address. That is a plausible shape for this kind of abuse, but it is my illustration, not a case from the reports.

    The Bottom Line

    One vendor reported one actor and at least 143 devices, using vulnerabilities that were already public. What we do not know is how widespread this is, which SAP systems were involved, or whether it continues. What we do know is cheap to act on: find your forgotten devices, retire the unsupported ones, and add residential proxy detection to your sign-in monitoring.

  • Ransomware Victims Report Threats Against Employees’ Families in a New Survey: Your Incident Response Plan Needs a Personal Safety Chapter

    Ransomware Victims Report Threats Against Employees’ Families in a New Survey: Your Incident Response Plan Needs a Personal Safety Chapter

    Search for “ransomware physical threats employees families” this week and you will find a burst of coverage built mostly on one source: Semperis’s 2026 Ransomware Risk Report. The numbers are alarming. They are also self-reported survey figures from a security vendor, and the reporters who looked at them said they could not independently confirm them. I think the topic deserves a place in your incident response planning anyway, and this post explains both halves of that.

    Ransomware Physical Threats to Employees’ Families: What the Survey Found

    First, who produced the data. Semperis, which sells identity recovery and crisis response services, says in its report that it partnered with research firm Censuswide, which surveyed “1,200 IT and security professionals” in nine countries and several industry sectors in the first half of 2026. The report says it “surveyed only organizations that were successfully attacked.” That means the percentages describe organizations that were already ransomware victims, not companies in general.

    Here are the figures as the report states them:

    • “Threatening texts, letters, or packages”: 57%.
    • “Threats against family or friends”: 37%.
    • “Physical intrusion”: 19%. “Abduction”: 17%. “Bodily harm”: 13%. “Stalking”: 6%.
    • On the effects: “doxxing,” 25%, and “swatting,” 23%. Swatting is defined in the report as “harassed by fabricated emergency reports that resulted in law enforcement being dispatched to their location.”
    • “More than half (53%) of respondents reporting that ransomware attackers carried through on threats in the past year.”

    The report also says “41% of respondents said they had been the target of physical or psychological intimidation.” Semperis’s October 14 press release gives slightly different versions: “40% of attacks involved psychological or physical threats against staff” and “24% of victims or family members were swatted.” The report’s body says 23% for swatting. I cannot tell which is a typo or a rounding choice, so treat these as roughly 40% and roughly a quarter. The press release also says “nearly 25%” faced psychological intimidation, while the report’s list of attacker threats shows psychological intimidation at 23% and physical threats at 17%. The denominators are not always clear. For example, the 57% figure appears to be a share of people who were threatened at all, as Dark Reading describes it, not a share of all respondents.

    CSO Online’s coverage repeats the survey figures, including that “37% said employees’ friends or family members had been threatened,” and notes the survey’s sample and scope. It does not add independent evidence of its own.

    What the Data Cannot Tell Us

    Dark Reading is the most cautious source, and its caution matters. It writes that Semperis’s study “relied on self-reporting, and it couldn’t corroborate these alarming figures, nor could Dark Reading.” It adds that “Dark Reading failed to find even a single documented case of violence perpetrated in service of a ransomware attack.” When it asked Semperis for a case study, Semperis pointed to a Europol release on so-called violence-as-a-service, which “did not connect violence-as-a-service with ransomware.” A Semperis incident response director told Dark Reading that physical harm “does happen” in “some way, shape, or form.”

    Dark Reading also notes year-over-year confusion: it says 40% of participants in Semperis’s 2025 report reported physical threats, while only 17% of 2026 respondents said they had been subject to physical threats. It also reports related trends in other crimes, such as violent “wrench attacks” in cryptocurrency theft, and says that “What’s true of cryptocurrency is not necessarily true of enterprise cyberattacks.” I am not citing those numbers here beyond noting that Dark Reading frames them as adjacent, not proof.

    So the responsible reading is this. One vendor survey says a large share of attacked organizations report personal threats, including against families. Independent verification of violence is missing, and prevalence in the wider population of companies is unknown. I would not tell your executives that gangs are now routinely stalking employees’ families. I would tell them that credible-enough reports of family-directed threats exist, and that a plan for them costs little.

    What the Report and Coverage Recommend

    Semperis’s report advises documenting “roles not just within the cybersecurity team, but across the entire enterprise,” establishing out-of-band communications, and including “procedures for how to respond to incidents that involve places and people outside the organization, such as threats against family members,” including reaching out to local and federal law enforcement in advance. CSO Online’s article says that employees should have “a confidential channel to report intimidation” and that HR, legal, cybersecurity and corporate security teams should know when to escalate to law enforcement. It also quotes the CEO of the consultancy Primus Partners saying the organization should “minimize information retention and access to sensitive personal information of employees.” Those recommendations come from vendor, media and consultant voices, not from regulators.

    My Recommendation: A Personal Safety Chapter

    This section is my opinion. The checklist is my own, built on the sources above, and no source requires it.

    Picture this hypothetical. During an incident, a member of your on-call team tells their manager that someone has contacted a relative. If the runbook has nothing to say, the manager improvises, and the employee may feel alone with the problem. A short chapter prevents that.

    1. Name an owner. Pick one person from HR, legal or corporate security who handles personal-safety reports during incidents.
    2. Give staff a private reporting path. Make it clear how to report any contact or threat, with no penalty and no need to prove it first.
    3. Pre-build the law enforcement contacts. Know whom you would call locally and federally before you need them.
    4. Decide support up front. Agree in advance what help you can offer affected staff, such as counseling or security advice, and who can approve it.
    5. Reduce exposed employee data. Review what personal information about staff sits in company systems and public profiles, and cut what you do not need.
    6. Separate safety from the ransom decision. Document who decides how to respond to threats against people, and keep that apart from the technical recovery plan.
    7. Rehearse it. Add one personal-threat inject to your next tabletop.

    The Bottom Line

    The evidence is one vendor survey with self-reported answers and independent coverage that could not verify it. The planning cost is small, and the downside of having no plan is borne by people. That is why I would add the chapter, while being plain about what we do and do not know.

  • Ivanti Zero-Days Gave Attackers Root on a VPN That Was Fully Patched at the Time: Why Your Remote Access Appliance Needs a Compromise Plan, Not Just a Patch Plan

    Ivanti Zero-Days Gave Attackers Root on a VPN That Was Fully Patched at the Time: Why Your Remote Access Appliance Needs a Compromise Plan, Not Just a Patch Plan

    Patching on day one is the standard advice for edge devices. This week’s Ivanti news shows the limit of that advice. Volexity reports that an attacker used a chain of three zero-days against an appliance that was fully patched at the time, and the lesson for Ivanti Connect Secure zero-day VPN security is that a patch plan alone is not enough. You also need a plan for the day you find out the box was already owned.

    What Volexity Found

    In its October 13, 2026 report, Volexity says that in the first week of October it “discovered an unknown threat actor, UTA0576, abusing a zero-day exploit chain to compromise a fully patched (at the time, version 22.8R2.4) Ivanti Connect Secure (ICS) VPN appliance.” The chain “combined an authentication bypass, a remote code execution (RCE), and a privilege escalation vulnerability to achieve unauthenticated root-level code execution.”

    Two details matter. First, “fully patched” describes that one appliance at that moment. Volexity describes a single investigation at one customer, and I am not claiming this was a broad campaign. Second, Volexity says exploitation began on October 3, 2026, and that it started its investigation on October 5.

    After getting in, Volexity says UTA0576 “primarily focused on credential theft, data exfiltration, log tampering, and network reconnaissance.” It lists:

    • Extracting credentials stored on the appliance, “such as domain credentials used with LDAP.”
    • Searching Active Directory for LAPS local administrator passwords and BitLocker recovery keys.
    • Password spraying and packet capture of LDAP traffic from the appliance.
    • Removing entries from the appliance’s debug log and Linux audit log.

    SecurityWeek adds Volexity’s view that the actions pointed to “preparation for lateral movement and a wider compromise of the network.” Volexity found no backdoor or web shell, because, as Volexity puts it, it “did not identify first-stage malware or web shells that would have enabled the threat actor to execute commands without re-exploiting” the appliance. The entire chain ran for each command, with results returned in the HTTP response.

    That is why detection is hard. Volexity says Ivanti’s Integrity Checker Tool “does not detect any modifications” because the exploit patches code in memory and restores configuration data afterward. “As such, forensic investigation is required to identify evidence of exploitation.”

    Ivanti Connect Secure Zero-Day VPN Security: What Is Patched as of October 15

    Ivanti is tracking the authentication bypass and the RCE under CVE-2026-104935. SecurityWeek reports those are patched in ICS versions 22.8R2.5, 25.1.1.2, 25.1.3.0 and 25.1.3.1. Ivanti’s own October Patch Tuesday post lists the same fixed builds and says Ivanti is “aware of limited exploitation.”

    The third flaw is a privilege escalation in how the dsinvoked service trusts DSCache configuration data. Volexity says “Ivanti is working on a fix for the privilege escalation vulnerability, and it will be included in a future release in the coming weeks.” SecurityWeek says it “remains unpatched.” Ivanti’s post describes “a fix for a related privilege escalation flaw used in the same chain” as “due in the coming weeks.” I checked again today, October 15, and found no report of a released fix. I could not read Ivanti’s advisory page itself, which is a script-loaded page, so that status rests on Volexity, SecurityWeek and Ivanti’s blog. Verify it on Ivanti’s site before you act.

    Do not tell your leadership “all three are patched.” Two are. The third is, by these sources, still open.

    What CISA Says

    In its October 13 alert, CISA says it “added CVE-2026-104935 to its Known Exploited Vulnerabilities (KEV) Catalog on Oct. 13, 2026,” and that “Organizations seeking to determine whether they were compromised will need to conduct network and memory forensics.” The KEV entry in CISA’s catalog data lists a due date of October 16, 2026. For suspected compromise, CISA recommends actions from Ivanti’s recovery procedures: back up the configuration, “conduct a factory reset and upgrade the appliance to the latest version” (rebuild virtual instances), restore the configuration, and “reset passwords for all accounts, including domain, administrator, and local accounts,” plus revoke and reissue stored certificates and reset stored API keys.

    CISA also notes that “Ivanti Connect Secure version 22.8 reaches end of life on Jan. 31, 2027,” which Ivanti’s post echoes while recommending a move to 25.x.

    A note on other vendors. Ivanti’s Patch Tuesday post says edge devices “dominated the weeks before this Patch Tuesday,” citing a Citrix NetScaler zero-day and a SonicWall SMA1000 flaw. SecurityWeek separately reports exploitation attempts against SonicWall’s CVE-2026-102255 starting October 8, after an October 6 disclosure. None of those sources ties these cases to the Ivanti activity, so treat them as a pattern of edge-device attention, not one campaign.

    My Compromise Plan for a Remote Access Appliance

    This checklist is my own recommendation. The sources above do not prescribe it, apart from the CISA recovery steps already quoted.

    1. Patch now, then assume nothing. Apply the fixed build for your code line. Treat the patch as closing the door, not as proof nobody came through it.
    2. Hunt back to early October. Volexity suggests watching for large numbers of requests to welcome.cgi and for mismatches between the URL path and the X-DSCGI-PATH header, and checking /tmp for post-exploitation files.
    3. Look for movement from the appliance. Volexity says systems showing “attempts to move laterally originating from the ICS VPN device” should be forensically investigated. Review directory service queries and logins from the appliance’s service account.
    4. Plan the credential reset before you need it. The appliance can hold domain credentials. Know which service accounts it uses and how you would rotate them, along with certificates and keys.
    5. Limit what the box can reach. Give its service account least privilege and put internal segmentation behind it, so root on the appliance is not a master key.
    6. Keep logs off the box. Volexity says the attacker edited local logs. Forward logs and network telemetry elsewhere.
    7. Rehearse a rebuild. Know who can factory reset and reload the appliance, how long it takes, and what remote access you offer meanwhile.
    8. Know your end-of-life dates. If you run 22.8, plan the move to 25.x now.

    The Takeaway

    This is my view: a patch plan answers “are we on the latest version?” A compromise plan answers “if this box were owned last week, would we know, and what would we do?” For the device sitting at your network edge, you need both, and this week’s reporting shows why.

  • An Executive at a Ransomware Negotiation Firm Was Arrested in the ShinyHunters Probe: How to Vet the Incident Response Firms You’d Call on Your Worst Day

    An Executive at a Ransomware Negotiation Firm Was Arrested in the ShinyHunters Probe: How to Vet the Incident Response Firms You’d Call on Your Worst Day

    Most companies sign an incident response retainer once, file it, and never look at it again. That retainer names the people who would see your most sensitive data, talk to your attackers, and possibly move your money on the worst day your company has. This week’s news is a good prompt to treat ransomware negotiation firm vetting incident response planning as a trust decision you revisit, not a box you checked once.

    What Was Reported, and What Is Confirmed

    On October 9, FBI Director Kash Patel announced that agents had arrested “another suspected co-conspirator of the ShinyHunters group,” as BleepingComputer reported. Patel did not name the suspect. ShinyHunters is the extortion group the FBI holds responsible for the September breach of its jobs portal.

    KrebsOnSecurity reported that the FBI arrested “an executive at a Canadian cybersecurity firm in connection with an investigation into the ShinyHunters hacking group,” citing multiple sources. Press reports identify the man reportedly arrested as Edward Dubrovsky, 54. The FBI has not publicly confirmed that he is the person Patel described. BleepingComputer says plainly: “While the FBI has not publicly confirmed that Dubrovsky is the suspected ShinyHunters co-conspirator, KrebsOnSecurity reports that multiple sources linked Dubrovsky’s arrest to the ShinyHunters investigation.”

    The court record is more concrete, and it spells the name differently. A federal docket indexed on CourtListener, United States v. Dobrovsky in the Eastern District of Pennsylvania, shows an arrest on October 8. It lists the complaint charges as:

    • “CONSPIRACY TO THREATEN TO IMPAIR THE CONFIDENTIALITY OF INFORMATION WITH THE INTENT TO EXTORT MONEY”
    • “INTERFERENCE WITH COMMERCE BY THREATS (HOBBS ACT EXTORTION AND CONSPIRACY TO COMMIT HOBBS ACT EXTORTION)”

    A commitment order dated October 9 sends the defendant to the Eastern District of Texas, where the charges were filed. The complaint itself is sealed. BleepingComputer notes that “it is still unclear what he is accused of doing or whether the case is connected to the FBI breach.”

    These are allegations. Dubrovsky has not been convicted of anything, and he is presumed innocent. Prosecutors have not said the charges involve his negotiation work, and I am not suggesting they do.

    What the Firms Say

    Descriptions of his role vary, so here is what each source says. KrebsOnSecurity reported that LinkedIn listed him as one of CYPFER’s “ex-founders,” and that he is “now associated with another Canadian security firm and sponsor called CyberSteward.” CyberScoop describes CYPFER as “a firm that helps organizations negotiate with ransomware operators,” and CyberSteward as “a Toronto-based firm that helps breach victims negotiate ransom payments.”

    CYPFER disputes the founder label. A firm representing CYPFER told CyberScoop that his role “was Managing Director from May 2022 through Dec. 2025,” and that he “had no affiliation, operational role or relationship with CYPFER since that time, and contrary to certain reporting, was never a founder or co-founder of the company.” I found no published statement from CyberSteward.

    Did he do negotiation work himself? The sources point that way without proving it. Krebs quotes a LinkedIn post in which he wrote of “advisory, negotiations and settlement services,” and one of Krebs’s sources said “the suspect’s company specialized in handling ransomware negotiations with cybercrime groups.” He also recently published a book, Cyber Extortion Strategic Response, about handling cyber extortion.

    One more line from Krebs is the reason this matters beyond one case. Sources told KrebsOnSecurity that “charges against principals at other companies that specialize in ransomware negotiation may be forthcoming.” That is unconfirmed, and I would treat it that way.

    Why an IR Retainer Is a Trust Relationship

    From here on, this is my opinion and my own recommendation, not something any source above prescribes.

    Think about what you hand an incident response or negotiation firm during a crisis. You give them access to your environment, your stolen data samples, your executives’ phone numbers, your insurer, and sometimes your payment process. You give them direct contact with the people extorting you. Few vendors get that much trust that fast, and most companies picked theirs from an insurer’s panel list years ago.

    Picture this hypothetical. Your company is hit, you call the firm on your retainer, and the negotiator assigned to you works through a channel nobody on your side can see. If that person, or anyone at the firm, were ever compromised or conflicted, you would have little way to know. Nothing in this week’s case shows that happened to any client. The point is that most retainers are not built to detect it if it ever did.

    My Ransomware Negotiation Firm Vetting Checklist for Incident Response

    This is what I would do, and it is my recommendation only:

    1. Re-vet the firm every year, not just at signing. Confirm who owns it, who runs it, and whether anything has changed. Check the names on the retainer against current news and court records.
    2. Know the individuals, not just the logo. Ask which people would actually work your case and negotiate, and what background checks the firm runs on them.
    3. Ask how they prevent conflicts of interest. Ask whether they have policies against staff having any relationship with threat actors beyond case communication, and how they enforce them.
    4. Keep visibility into every attacker conversation. Require that all negotiation messages be logged and shared with your counsel and your internal lead, with no side channels.
    5. Split the money from the talking. Any payment decision and movement of funds should need approval from your own executives and counsel, with documented checks, not just the negotiator’s word.
    6. Have a second option ready. Keep an alternate firm pre-approved with your insurer, so you are not stuck with one vendor if you lose trust mid-incident.
    7. Put audit rights in the contract. Ask for the right to review case records, data handling, and staff access after an incident closes.

    The Bottom Line

    One sealed complaint does not tell us what happened, and the person charged has not been convicted. What it does is remind us that the vendors we would call on our worst day deserve the same scrutiny we give any other privileged access. Review that retainer before you need it.

  • Attackers Are Exploiting AhsayCBS Flaws to Take Over Backup Servers: Your Recovery Plan Is Now an Attack Surface

    Attackers Are Exploiting AhsayCBS Flaws to Take Over Backup Servers: Your Recovery Plan Is Now an Attack Surface

    Backup servers are supposed to be the boring, trusted box in the corner that saves you on your worst day. This week is a reminder that attackers see them differently. Huntress reports that threat actors are chaining two AhsayCBS flaws to run code on exposed backup management servers, and the vendor’s first patch did not fully close the hole. If you treat AhsayCBS vulnerability backup server security as a quarterly checkbox, now is the time to treat it as an active incident.

    What Huntress Saw in the AhsayCBS Attacks

    AhsayCBS (Cloud Backup Server) is the management console for Ahsay’s backup software. In its October 8, 2026 writeup, Huntress says it is “primarily used by managed service providers (MSPs) and system integrators” and that it “centralizes control of backup operations.” That makes it a high-value spot: one console, many customers’ backups.

    Huntress says NVD disclosed two CVEs on October 4, 2026:

    • CVE-2026-105133, which Huntress describes as “a medium-severity flaw” in the checkSysPwd function that “can lead to improper authentication.”
    • CVE-2026-105134, described as “a critical-severity vulnerability” in the Replication Receiver component that “can be exploited to achieve unauthenticated remote code execution as NT AUTHORITY/SYSTEM on the host.”

    According to Huntress, attackers are chaining them: “First, CVE-2026-105133 is used to bypass authentication. Then CVE-2026-105134 is used to gain code execution.” Huntress says exploitation started on October 7 at 23:20:15 UTC, which is 7:20 PM ET. It adds that “As of October 8, Huntress has seen five organizations targeted via these flaws.”

    Here is what Huntress documented after the attackers got in:

    • Webshells. “In some incidents we saw threat actors deploy .jsp webshells in the web application directory immediately after exploitation.”
    • A disguised cryptominer. “On several endpoints we observed the XMRig miner (edge.exe), renamed to masquerade as a Microsoft Edge process.”
    • Persistence. A Windows service named MicrosoftEdgeUpdateSvc, built to look like the real Edge Update service, which ran a modified copy of the NSSM utility with SYSTEM privileges.
    • Hiding tricks. A PowerShell script, Taskgmr.ps1, that Huntress says “appears to be an AI-assisted script.” It stopped the miner’s service while Task Manager was open.
    • A vulnerable driver. In one incident, attackers downloaded WinRing0x64.sys. Huntress says it gave the miner kernel-level access to the hardware.

    Huntress does not name an attacker, and its report does not describe any data theft or tampering with backups. I am keeping that scope. What it documents is SYSTEM-level code execution, webshells and mining. That is bad enough on a box that controls backups.

    The Patch Story: Incomplete, Then Corrected

    I would not call these flaws unpatched. A fix exists. But the timeline has a twist every operator should know. Ahsay’s own October 10, 2026 security alert says: “our previous patch v10.3.4.0 did not fully address the following security vulnerabilities,” naming both CVEs. It tells partners that “Partners running affected v10 versions should apply the AhsayCBS v10.3.4.45 hotfix” and adds: “After applying the hotfix, please reboot your server.” Ahsay says a partner portal login is required to download it.

    Huntress’s own updates track the same correction. On October 8 it said 10.3.4 “is also affected,” noting that “Previous reporting indicated that 10.3.4 was not susceptible.” Its October 12 update says it “independently verified that the AhsayCBS 10.3.4.45 hotfix mitigates the initial entry point of this attack chain.” Huntress also says companies on AhsayCBS v7, v8 and v9 “should apply the 9.15.2.70 hotfix.” Ahsay’s alert only mentions v10, so check your version against both pages.

    The lesson there is simple. If you patched to 10.3.4.0 and moved on, you are not done.

    AhsayCBS Vulnerability Backup Server Security: What Operators Should Do Now

    Huntress recommends restricting management interface access “to trusted IP addresses only or require VPN.” If you find any of its indicators, it says to “carry out a full host re-image from a trusted backup; as attackers have been able to hide secondary backdoors for extended persistence.” My checklist, built on those two sources plus my own judgment:

    1. Apply the hotfix and reboot. For v10, that is 10.3.4.45 per Ahsay. Confirm the reboot actually happened.
    2. Get the console off the open internet. Allow-list trusted IPs or put it behind a VPN, as Huntress advises.
    3. Hunt before you relax. Huntress publishes indicators and four Sigma rules. Look for unexpected child processes from cbssvcX64.exe, .jsp files in the web app directory, a MicrosoftEdgeUpdateSvc service, Edge-named binaries in Temp folders, WinRing0x64.sys, and outbound traffic to mining pools on port 8029.
    4. Re-image if you find a hit. Do not just delete the webshell. Huntress’s guidance is a full rebuild from a trusted backup.
    5. Review downstream access. If the console has credentials or agents tied to customer environments, check whether any of those were used during the exposure window.

    Opinion: Your Recovery Plan Is Now an Attack Surface

    This section is my opinion, not a finding from Huntress or Ahsay. In this campaign, the documented payoff was cryptomining. But think about what SYSTEM access to a backup console could mean in a different campaign. Imagine an attacker who quietly changed retention policies or disabled jobs weeks before a ransomware event. You would not find out until you tried to restore. That scenario is hypothetical, but the access needed to attempt it is exactly what these flaws grant.

    So I treat backup management the way I treat domain controllers. Keep it off the internet. Give it separate admin credentials with MFA. Monitor it like a crown-jewel system. Test restores from copies the console cannot delete or change. If your recovery plan depends on a box anyone can reach from the internet, the plan is part of your attack surface.

  • Anthropic’s Cyber Verification Program Reduces Claude Security Blocks for Verified Defenders: Who on Your Team Should Hold the Badge

    Anthropic’s Cyber Verification Program Reduces Claude Security Blocks for Verified Defenders: Who on Your Team Should Hold the Badge

    Picture this: your building hands out a new master key, and only people who pass a background check can get one. That sounds sensible until you are the one deciding which of your employees carries it, which doors it opens, and who reviews the log afterward. That is roughly the governance question Anthropic’s Cyber Verification Program now puts in front of security teams. The program reduces some Claude security blocks for verified defenders, and it hands each organization the job of deciding who internally gets the sharper tool.

    Here is what Anthropic actually documents, what it does not, and the questions I would want answered before turning it on.

    What the Anthropic Cyber Verification Program Changes for Claude Security Work

    Anthropic’s October 6, 2026 announcement describes an “expanded version” of the Cyber Verification Program, or CVP. It says the CVP “makes advanced cyber capabilities and reduced blocking classifiers available to qualifying security professionals.” The starting point matters. Anthropic says its generally available models, such as Claude Opus 5.5, Claude Fable 5.1 and Claude Sonnet 5.5, “have conservative cyber safeguards that block most cyber work.” Its reasoning is that cybersecurity is “inherently dual use”: the same capability that helps a team find and fix a flaw can help an attacker exploit it.

    The general models are not useless for security. Anthropic’s Help Center page for the program says they can still be used for secure code review, threat modeling, patching known issues, finding vulnerabilities in your own source code and triaging alerts. But it warns that “other cyber security work like malware analysis or exploit validation may be interrupted by our safety classifiers.” The CVP is the route for professionals whose legitimate work is getting blocked.

    This is also a merger. Anthropic says that for the past six months it ran two programs: Project Glasswing, which gave organizations securing critical software access to Claude Mythos, and the original CVP, which gave vetted teams “access to reduced safeguards on Claude Opus and Claude Sonnet models.” The new CVP integrates both. Each tier includes Claude Opus 5.5, Claude Sonnet 5.5, Claude Mythos 5.1 and future models.

    Three Tiers, Documented

    Anthropic documents three access tiers, each with “different verification requirements and security controls”:

    • Defense Access covers defensive work such as SOC and incident response tasks, reverse-engineering malware, and analyzing and validating vulnerabilities. Anthropic’s examples of qualifying organizations include corporate, nonprofit, university and government security teams defending their own systems; critical infrastructure operators of any size; smaller security firms; open-source maintainers; and individual researchers with a track record of reported vulnerabilities. It is the only tier open to individuals, and only on a paid plan.
    • Red Team Access adds authorized penetration testing and red-teaming, for organizations only. Testing is limited to systems they are authorized to test. Anthropic says users “will still experience real-time blocks” on actions that could cause physical harm or mass disruption, such as deploying ransomware or damaging physical systems.
    • Specialized Access “has the fewest cyber blocks.” It is reserved for a limited set of verified organizations authorized to test safety systems such as flight operating systems, power grids, telecom networks and interbank transfer infrastructure. Anthropic says it reviews every one of them “in depth in collaboration with the US government,” and existing Glasswing members move into this tier.

    Anthropic also published results from its own evaluation, CyScenarioBench, run against Claude Opus 5.5 under each tier’s safeguards. It reported that without CVP every task was blocked on the first prompt, and that in Defense Access 46 of 50 trials were blocked at some point. In Red Team Access there were no blocks, and the model completed 34 of 50 tasks. That is vendor-run testing on a vendor-built benchmark, so read it as Anthropic’s evidence that the tiers behave differently, not as independent validation.

    Who Checks the Badge

    Here the documentation is useful but not complete. Anthropic says it “will verify all applicants and request proof of the required security controls for the relevant access tier.” The Help Center lists what an application needs: organization and applicant details for identity verification, a description of your security work, and “an attestation to the security controls applicable to your desired tier.” Organizations apply once, and admins then designate seats or assign the program to workspaces or custom roles. Anthropic aims to answer within seven business days and places each applicant “at the highest tier” its information supports. The announcement adds that Red Team reviews take “a few weeks.”

    The Help Center also lists factors that can rule an organization out. These include the nature of the work, whether Anthropic can verify who the organization is, the legal and regulatory environment and the risk access “could be compelled,” and a more cautious approach for organizations that primarily serve military, intelligence or law enforcement customers.

    A few strings stay attached. The Usage Policy “still applies in full.” Anthropic says it “may review, narrow, or withdraw a grant.” Data retention is required “so that we can monitor for cyber misuse,” with limited zero-data-retention exceptions until Anthropic’s Enterprise Frontier Safeguards option arrives. Defense Access members have until December 15, 2026 to adopt phishing-resistant MFA and stop using API keys. CVP access also cannot be used to build a client-facing product without a separate approval.

    What is not public: the exact scoring behind tier placement, how attestations are checked in practice, and precisely which classifier behaviors change in each tier beyond Anthropic’s examples. SecurityWeek’s coverage matches Anthropic’s description of the three-tier structure, but I have not seen independent detail beyond that.

    Opinion: The Real Badge Check Happens Inside Your Org

    This section is my opinion. Anthropic is checking the organization. Once a grant lands, your admins decide which workspaces, roles and seats get it. That makes CVP an internal privileged-access problem as much as a vendor program, and I would govern it like one:

    • Map the tier to job duties. Only people whose work actually needs malware analysis or exploit validation should sit in a CVP-enabled workspace.
    • Treat the workspace like a privileged group. Use named seats, periodic access reviews, and removal on role change.
    • Log on your side too. Anthropic retains data for misuse monitoring, but that is its monitoring, not yours. Keep your own record of who used the elevated workspace and for which engagement.
    • Get the controls done early. Phishing-resistant MFA and moving off API keys are good hygiene anyway, and the deadline is documented.
    • Write down scope. Red Team Access is limited to systems you are authorized to test. Keep that authorization paperwork next to the access list.

    A sharper tool for defenders is a reasonable idea. The part that will decide whether it stays reasonable is the boring part: who holds the badge, and who reads the log.