Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

Category: Security

  • Microsoft Says Attackers Abuse GSocket for Linux Backdoor Persistence That Survives Patching: Hunting for the Access That Outlives the Fix

    Microsoft Says Attackers Abuse GSocket for Linux Backdoor Persistence That Survives Patching: Hunting for the Access That Outlives the Fix

    Patching the hole an attacker came through is not the same as evicting the attacker. Microsoft’s latest threat research puts a sharp point on that: attackers are abusing GSocket, a legitimate open-source connectivity tool, to build Linux backdoor persistence that keeps working after the web application flaw behind the break-in is fixed. If you close an incident when the patch ships, the report suggests you may be closing it early.

    What GSocket Is, and What Microsoft Reported

    GSocket is the Global Socket Toolkit. Its project page describes it as a way for two users behind NAT or a firewall to establish a TCP connection with each other, using the Global Socket Relay Network, a free cloud relay, and a shared secret in place of IP addresses. Its gs-netcat tool can give a remote shell. It is released under the BSD-2-Clause license. The tool is not malware by nature, though Defender flags it as a “GsNetcat” hacktool. What matters here is how it is used.

    In a report published November 11, 2026, Microsoft Security Research authors Yash Gund and Sumith Maniath said Microsoft observed multiple incidents in which threat actors deployed GSocket on compromised Linux servers “to maintain access even after the vulnerabilities used for initial compromise were remediated.” The report does not name a threat actor. It says “multiple unrelated threat actors have adopted it,” and it names no vulnerability used for initial access beyond saying internet-facing web applications were exploited.

    Why a Patch Does Not Remove It

    Microsoft’s explanation is brief: “Because GSocket runs independently of the exploited application, patching the vulnerability does not remove the relay client or its persistence.” The web exploit gives command execution only while the hole stays open. The relay client does not need the hole.

    Microsoft describes three properties that make it attractive to attackers. Traffic passes through a shared public relay, so there is no attacker-owned IP address or domain to block. Both the server and the operator connect outbound, so inbound firewall rules never see the session. And the deployment script can rename the process, stage files in memory-backed directories, and install persistence that survives a reboot.

    What the Linux Backdoor Persistence Looks Like

    In the observed intrusions, attackers used curl to download and run a script, which profiled the host, picked a client for the architecture, and staged it in writable or memory-backed paths such as /dev/shm. Microsoft says attackers then disguised the process with kernel-thread-like names (one example is [kaluad]) and persisted through “cron, systemd, shell profiles, watchdogs, and redundant copies.” They also removed staging files. Microsoft’s examples include a defunct.service unit, a renamed payload at /usr/bin/defunct, a binary called systemd-remount-d, and a hidden /dev/shm/.gs-0 directory.

    Reconnection works through a secret rather than an address. The deployment script typically generates it and, per Microsoft, the operator can read it from the console, retrieve it from a temporary file, or have it delivered through Telegram, Discord, or a webhook. With the secret, the operator can reconnect later from any compatible client.

    In a few incidents, Microsoft says, attackers who had execution as the web-service account tried to escalate to root using CVE-2026-43284, one of the Linux kernel flaws known as Dirty Frag. Microsoft says “attempted,” and it does not say every attempt worked. Ubuntu’s advisory says the Dirty Frag flaws were publicly disclosed on May 7, 2026, covers two CVEs (CVE-2026-43284 and CVE-2026-43500), and says kernel updates are available and need a reboot. Check your own distribution for both.

    What Microsoft’s Telemetry Shows

    This is vendor telemetry, from Microsoft Defender for Endpoint, and it reflects Microsoft’s customers. From March through August 2026, Microsoft says devices with GSocket-related detections rose 356.2%, “although the increase was not consistent month to month.” Web applications and hosting made up 87.1% of attributable incidents. Within that group, PHP web applications and cPanel hosting were 63.9% and Apache 24.3%. Education and research was the largest sector at 30.7%, followed by technology and telecommunications at 22.9%. Microsoft cautions that exposure is the more likely factor than deliberate targeting, noting that academic institutions often run large, decentralized web estates maintained outside central IT.

    Microsoft also notes limits. Not every stage occurred in every intrusion, and persistence across reboot and successful relay sessions were not confirmed in every case. The published indicators are specific observations, “rather than a complete inventory.”

    A Hunting and Cleanup Plan for Patched Servers

    Microsoft’s report includes Defender alert names, Advanced Hunting queries, and an IOC list of domains, file paths, and SHA-256 hashes. Its mitigation guidance tells defenders to remediate the host as well as the vulnerability: investigate and remove the client, its persistence, and staged files, “then verify that outbound connections to the relay infrastructure have stopped.” Using that guidance, here is how I would run it.

    1. Audit persistence first. Review cron entries, systemd units with plausible service names, shell startup files, and watchdog scripts. Microsoft notes persistence is often layered, so killing the process alone does not remove access. Remove the persistence before the process, or it comes back.
    2. Hunt by behavior. Look for shells launched by PHP, Java, or Node web processes, execution from hidden or world-writable paths, and processes whose names imitate kernel threads but do not belong to the kernel. Run Microsoft’s published queries if you use Defender XDR.
    3. Constrain egress. Microsoft recommends deny-by-default outbound rules and monitoring connections to relay infrastructure. A web server should not need to reach arbitrary hosts.
    4. Harden temp paths. Mount temporary and memory-backed directories non-executable where feasible, as Microsoft advises.
    5. Patch the local privilege escalation path. Prioritize kernel updates on internet-facing servers, including the Dirty Frag fixes, and schedule the reboots.
    6. Treat credentials as exposed. This one is my judgment, not Microsoft’s: if an attacker held a shell on the host, rotate the secrets the web application can read, such as database passwords and API keys.

    When a Cleaned Server Is Still Suspect

    Microsoft’s guidance is to remove the tool and verify. If you cannot establish whether the attacker reached root, or what else was changed, my view is that rebuilding from a known-good image is the safer path. That is an opinion, and the cost is real downtime. The report gives you the checks for the specific tool, and it cannot tell you what else an attacker with a working shell did.

    The lesson is a change in what counts as done. A closed vulnerability is the start of the cleanup, so add a host check to the end of every web-compromise ticket.

  • CISA Says Cisco BroadWorks Vulnerability CVE-2026-20320 Is Being Exploited Months After Its Fix: Bringing Voice and Telephony Platforms Into Your Patch Program

    CISA Says Cisco BroadWorks Vulnerability CVE-2026-20320 Is Being Exploited Months After Its Fix: Bringing Voice and Telephony Platforms Into Your Patch Program

    The phone system is usually the last platform anyone patches. It belongs to a different team, runs on a vendor’s release train, and has a service window nobody wants to schedule. That habit now has a federal deadline attached. On November 10, CISA added the Cisco BroadWorks vulnerability CVE-2026-20320 to its Known Exploited Vulnerabilities (KEV) catalog, nearly three months after Cisco published its advisory and fixed releases. If your company, or your service provider, runs voice or unified communications on BroadWorks, here is what is confirmed, what is only reported, and what belongs in your patch program.

    What the Cisco BroadWorks Vulnerability Allows

    Cisco’s security advisory was first published on August 19, 2026, and rates the flaw High, with a CVSS base score of 7.5. It is an XML external entity (XXE) problem in the Open Client Interface (OCI) XML parser. Cisco says XML entries are improperly parsed “due to external entity resolution being allowed by default,” and an unauthenticated, remote attacker could send a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service and read sensitive files from the filesystem with the privileges of the BroadWorks user.

    Four components are affected when they run a vulnerable release, regardless of device configuration: the Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform. For all four, Cisco lists releases earlier than RI.2026.07 as affected, with RI.2026.07 as the first fixed release. Cisco says there are no workarounds. Upgrading is the remedy.

    What CISA Added and What It Requires

    The KEV catalog entry lists the vendor and product as Cisco BroadWorks, with a date added of 2026-11-10 and a due date of 2026-11-24, which is next Tuesday. The entry marks known ransomware campaign use as “Unknown.” CISA’s alert says the additions are “based on evidence of active exploitation” and the entry’s required action cites Binding Operational Directive 26-04.

    That directive binds Federal Civilian Executive Branch agencies only. Everyone else is not on the clock, but CISA’s alert says it “encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities.” For a service provider or a company that hosts voice for customers, the federal date is a useful forcing function even without a legal requirement.

    Who Says It Is Being Exploited

    Here the sources differ, and the difference matters. CISA’s listing rests on its evidence of active exploitation, and it has not published details about attacks. Cisco’s advisory went through two revisions on this point. Version 1.1 on November 12 was “updated to reflect known active exploitation.” Version 1.2 on November 13 was “corrected to state that this vulnerability was added to the CISA KEV,” adding that “Cisco does not have direct evidence of active exploitation.” So the advisory now says the flaw is on CISA’s list and does not confirm attacks itself.

    A threat-intelligence firm has gone further. This is vendor research, not a CISA or Cisco finding, and I have not verified it. In a post dated November 8, Malbear Labs, writing about a campaign it calls Operation Snowball, reports that an attacker used an AI-driven intrusion harness against a European telecom provider and exploited CVE-2026-20320 on a BroadWorks Xtended Services Platform, Release 23.0.1.1075, on port 2208. Malbear says it recovered the platform’s system identity private key and other credentials from that host. Malbear does not say CISA relied on its research, and neither CISA nor Cisco has linked the two.

    The practical reading: treat it as exploited, because CISA says so, and treat the details of who and how as unsettled.

    Eighty-Three Days

    From the advisory’s August 19 publication to the November 10 KEV listing is 83 days by my count. Any system still on a release earlier than RI.2026.07 has had a public advisory describing the bug for about that long. Why do telephony platforms fall behind? This is my opinion, not something the sources say. The platform often belongs to a separate voice team. The upgrade cadence is set by the vendor and often by a carrier customer. A telephony outage is visible immediately to every employee. Meanwhile the vulnerability scanner that drives patching for servers may never have seen the box.

    The flaw type adds to the risk. This bug reads files. It does not run code or crash the service, so nothing breaks, and nobody notices that configuration data or keys left the building.

    Bringing Voice Platforms Into the Patch Program

    These steps are my recommendations, based on the advisory’s facts and not on any guidance from Cisco or CISA.

    1. Inventory the four components. Find every Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform you run or depend on, including those a hosting partner operates for you. Record the release of each.
    2. Compare against RI.2026.07. Anything earlier is listed as affected. Since Cisco says there are no workarounds, the question is when you upgrade, and the answer should be before November 24 if you want to meet the federal date.
    3. Check who can reach OCI-P. The advisory says the exploit travels through the OCI-P service. Confirm that only provisioning systems that need it can connect, and review how that service is exposed to the internet.
    4. Assume file read means credential exposure. If a vulnerable system was reachable before you patched, consider which keys, certificates, and credentials live on that host and whether they should be rotated. Malbear’s report of a stolen system identity key shows what that can include, but that is a vendor claim about one campaign.
    5. Look for the quiet signs. Neither the advisory nor the KEV entry publishes indicators of compromise. Review logs for unexpected connections to the OCI-P service, and for new outbound connections from BroadWorks hosts, from August 19 onward.
    6. Put telephony on the same dashboard. Add voice platforms to the asset list, ownership list, and KEV watch that covers your servers and network gear. A separate team can still run the platform, but someone should answer for it when a KEV date arrives.

    What to Take From It

    A KEV listing for a fixed bug is a statement about the gap between availability of a patch and its installation. The gap is longest on platforms that sit outside the normal patch cycle, and a phone system fits that description. If you cannot say today which BroadWorks release you are on, find out before Tuesday.

  • Exploited Outlook Zero-Day Leaks NTLM Hashes: Why November’s Patch Tuesday Is the Moment to Start Retiring NTLM

    Exploited Outlook Zero-Day Leaks NTLM Hashes: Why November’s Patch Tuesday Is the Moment to Start Retiring NTLM

    When a Patch Tuesday ships more than a thousand fixes, the one that matters first is the one attackers already use. In November 2026, that is an Outlook zero-day, and it is an NTLM hash theft bug: open the wrong file and Outlook can hand your Windows authentication hash to a server the attacker controls. Patch it this week. Then use the scare to fix the real problem, which is a three-decade-old authentication protocol most of us keep around only because nobody has inventoried what still depends on it.

    How the Outlook Zero-Day Enables NTLM Hash Theft

    The bug is CVE-2026-124194, Microsoft Outlook Spoofing Vulnerability, released November 10. Microsoft’s Security Update Guide marks it Exploited: Yes and Publicly Disclosed: No, with an exploitability assessment of Exploitation Detected. Microsoft rates it Moderate with a CVSS 3.1 base score of 6.5. Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024; the fixed builds listed are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024, with Microsoft 365 Apps covered through the normal Office security release channel.

    The mechanics are short. According to Microsoft’s FAQ, an attacker sends a specially crafted message file and convinces the user to open it. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, and Microsoft says the flaw “discloses a user’s NTLMv2 hash to the attacker who could use this to authenticate as the user.” The Preview Pane is not an attack vector, so somebody has to actually open the file. Microsoft has not published details about the attacks it detected, so I am not going to guess who is behind them or how many organizations were hit.

    CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10 and set a November 24 remediation due date for federal civilian agencies. If you are not a federal agency, treat that date as a sanity check, not a grace period.

    Prioritizing One Fix Inside a Thousand-Fix Release

    You may have seen this month described as a record. Microsoft’s own data does not support that. Counting CVEs in the November Security Update Guide data that were issued by Microsoft as the CNA and first published on November 10, I get 1,093. The same count for October 13 comes to 1,408. Both are enormous, but November is the smaller of the two, so it is not a record. Third-party tallies differ depending on whether they include Edge, Chromium, Linux, and other non-Microsoft CVEs that Microsoft republishes, so check what a headline number actually counts before you repeat it.

    The practical point survives the correction. Severity sorting will not surface this bug on its own; a 6.5 Moderate sits below a long list of Critical ratings. The flags that should move it to the top are the exploitation status and the KEV listing. A workable triage order for a release this size:

    1. Exploited first. Anything Microsoft marks Exploitation Detected or CISA lists in KEV goes to the front, regardless of score. This month, that is the Outlook fix.
    2. Confirm the Office channel. Office fixes ride a different update path than the Windows cumulative update. Verify the build number on actual machines, not just the deployment ring status.
    3. Then the internet-facing and identity tier. Domain controllers, Exchange, and anything reachable from outside come next.

    Why This Bug Class Keeps Coming Back

    The patch closes one path. It does not change the underlying condition, which is that a Windows client will still offer an NTLM response to a server it should never have been talking to. Microsoft’s own description of NTLM, in its January 2026 post on disabling NTLM by default, lists the problems plainly: no server authentication, vulnerability to replay, relay, and pass-the-hash attacks, and weak cryptography. The same post notes NTLM has been part of Windows authentication for more than three decades and is already deprecated.

    Imagine a finance user in a 40-person office who opens a message file that looks like a forwarded invoice. On an unpatched machine, the outbound connection happens, the hash leaves the building, and nobody sees a prompt. That is a hypothetical, but it is the shape of the risk: the user did one ordinary thing, and the protocol did the rest.

    That is why the network layer matters as much as the patch. Microsoft’s guidance on securing SMB traffic says to block TCP port 445 outbound to the internet at the corporate firewall, and notes it is unlikely you need outbound SMB to the internet unless a cloud service such as Azure Files requires it. The same guidance recommends outbound firewall rules for laptops on untrusted networks, because those devices are not behind your perimeter firewall. I would put SMB signing and Extended Protection for Authentication on the same list for any service that still accepts NTLM, since both exist to blunt relay.

    A Realistic NTLM Retirement Plan

    Microsoft’s roadmap has three phases: enhanced NTLM auditing now on Windows Server 2025 and Windows 11 version 24H2 and later; IAKerb and a local Key Distribution Center, both described as pre-release, to remove common reasons for NTLM fallback, slated for the second half of 2026; and network NTLM disabled by default in the next major Windows Server and client releases. Disabled by default is not removed. Microsoft says NTLM will remain in the OS and can be re-enabled by policy, and its timelines are explicitly subject to change.

    The steps Microsoft lists in that post are the right order of operations:

    • Deploy enhanced NTLM auditing to find where NTLM is still used.
    • Map dependencies across applications and services, and prioritize remediation, including pushing application vendors to update.
    • Migrate and validate that critical workloads succeed with Kerberos.
    • Test NTLM-off configurations in non-production environments before production.
    • Adopt the Kerberos improvements as they become available.

    Notice what is not on that list: flipping a block switch on Monday morning. Audit before block. Every blocking control will break something you did not know about, often a printer, a scanner that writes to a share, or an old line-of-business app that only knows NTLM. The audit phase is how you find those before your users do. None of this is risk-free, and a staged rollout with a written rollback is cheaper than an all-hands outage call.

    What I Would Do This Week

    Push the Office update and verify builds. Confirm outbound 445 is blocked at the edge and test it from a laptop on guest Wi-Fi. Turn on NTLM auditing where your OS versions support it and let it collect for a few weeks. Then start the dependency list. The Outlook zero-day will be patched in a week or two. The NTLM inventory is the work that makes the next one of these a smaller story.

  • Healthcare Cyberattack Planning: Patient Portal Downtime Lessons From University Hospitals

    Healthcare Cyberattack Planning: Patient Portal Downtime Lessons From University Hospitals

    Healthcare cyberattack planning has to cover patient portal downtime, not just the servers behind it. Cleveland’s University Hospitals offers a concrete example: keeping clinical sites open did not preserve every digital route patients used to reach them. When the portal disappears, a technical isolation decision becomes a scheduling, medication, communications and payment problem. Restoring a login page is only one part of restoring the service.

    What University Hospitals Actually Said

    In its cybersecurity incident notice, UH says it detected “unusual activity” on October 22, 2026, activated response protocols and disconnected systems from the internet “out of an abundance of caution.” That is the supported description. It does not establish ransomware, patient-data theft or a confirmed breach.

    The notice’s November 2 update said hospitals, emergency departments and physician offices remained open. It also described the operational split: most applications on UH-owned servers were functioning, but could not exchange information outside UH. An application can be running while the service its users need is unavailable. Infrastructure monitoring and patient experience are not the same dashboard.

    On November 7, UH announced MyChart was accessible again, according to WKYC’s report quoting UH’s restoration statement. October 22 to November 7 is 16 calendar days: more than two weeks, not three. Those dates do not establish an exact outage duration to the hour.

    The statement warned that some features might remain limited and new results or other information could be delayed while data was reconciled. WKYC explicitly noted that the announcement did not update electronic prescribing. Portal access was a recovery milestone, not confirmation that every connected workflow had recovered.

    Healthcare Cyberattack Planning Starts With Patient Portal Downtime

    UH’s downtime notice described working alternatives rather than simply asking patients to wait. Its phones remained operational, but very high call volumes produced long holds. Patients with urgent care, result or medication questions were directed to their doctor’s office, rather than a main number that could only transfer them. UH asked patients not to call merely to confirm existing appointments unless their care team had contacted them about a change.

    Video visits moved to phone, Zoom or in-person appointments with instructions from the care team. Outpatient pharmacies remained open. When electronic prescribing was unavailable, UH said providers could print, fax or call in prescriptions when needed. That describes UH’s fallback; another organization must have its clinical, pharmacy and compliance teams approve alternatives appropriate to its own requirements.

    UH also directed patients with Quest Diagnostics testing to Quest’s results service. That was not a universal replacement: UH Specialty Lab and inpatient results still required MyChart or the doctor. Payment at the time of service was unavailable at its cashless facilities, although the notice offered separate automated-phone and online payment routes. These were different dependencies, with different workarounds.

    A Working Telephone Is Not a Capacity Plan

    My practical starting point would be a workflow inventory owned jointly by IT and operations. For each patient-facing function, record what the patient needs, which outside connection it depends on, the approved alternative and who owns the resulting queue. “Call the office” needs staffing, routing and a way to track completion. Otherwise, the fallback is a hold queue with a reassuring name.

    • Appointments: distinguish existing bookings from changes, cancellations and new requests. Keep patient instructions consistent with what scheduling teams can actually deliver.
    • Medications and results: name the clinical escalation owner and the approved handoff. Track receipt and follow-up rather than treating a fax transmission as a completed patient task.
    • Payments: separate an unavailable collection channel from the underlying balance. Have finance explain permitted alternatives without implying every patient must use a portal.

    This is operator analysis drawn from UH’s documented workarounds, not a claim that UH used this exact inventory. I would exercise the alternatives under sustained demand, including shift changes and unavailable staff. A plan that works for a quiet afternoon may not remain workable after repeated days of diverted requests.

    Status Updates Are Part of the Recovery System

    The public messages also need reconciliation. On November 10, UH’s incident page still displayed its November 2 update and wording that MyChart was offline, despite the later restoration announcement. The dated announcement is evidence of restored access; the older page is not evidence of a fresh outage.

    There was still a narrower limitation afterward. In its November 8 update, cleveland.com reported a UH spokesperson’s statement that bill pay was the only remaining out-of-service portion of the portal. That does not establish that electronic prescribing, a separate workflow, had recovered. Neither an expected billing fix nor portal availability supplies a verified e-prescribing restoration date.

    I would give every status update an effective date, a named owner and a service-by-service description. When a newer notice supersedes an older one, link them and remove contradictory instructions. Patients should not have to debug the organization’s communications history to find a working route to care.

    Keep the Downtime Team Through Reconciliation

    HHS’s ASPR TRACIE Healthcare System Cybersecurity: Readiness & Response Considerations treats recovery as a continuation of downtime. It recommends planning the paper-document lifecycle, maintaining consistent communications and supporting the migration of manual documentation back into electronic systems. It also warns that partial functionality can hinder workflows or increase risk. These are planning considerations to adapt, not one configuration for every provider.

    My recovery checklist would therefore test complete workflows: request received, routed, acted on, documented and visible to the appropriate patient or team. Clinical leaders would decide how to reconcile medication requests and results safely; operations would retain staff for the backlog. The finish line is not merely an available portal. It is knowing what happened while the portal was unavailable, what remains unfinished and who is responsible for closing the loop.

  • RMM Tool Vulnerability: MSP Security Lessons From N-able’s N-central Shutdown

    RMM Tool Vulnerability: MSP Security Lessons From N-able’s N-central Shutdown

    An RMM tool vulnerability is an MSP security problem before it becomes a patching task. Remote monitoring and management concentrates the authority used to maintain customer machines. When that management plane becomes suspect, the same team must contain risk, preserve evidence, and keep customers working without its usual controls. N-able’s November 9, 2026 N-central shutdown makes that dependency concrete. The lesson is not that every management agent is malicious. It is that your recovery plan cannot depend entirely on the system you might need to disconnect.

    What N-able Actually Took Offline

    N-able’s status dashboard recorded the critical N-central incident starting November 9 at 10:15 AM EST. The company said it took its hosted N-central environments offline as a precaution while responding to publicly disclosed vulnerabilities. Its affected-services list covered hosted N-central in the Americas, APAC, and Europe. It also strongly advised on-premises customers to temporarily take their N-central servers offline until further guidance. That is not a shutdown of every N-able cloud product.

    The notice distinguished the unavailable hosted N-central classic environment from Ecoverse services available through N-able Login, including Asset View, Patching, Vulnerability Management, scripting, policies, and tagging. That distinction matters when building a fallback: unavailable management functions and available alternatives are not interchangeable, and neither should be guessed from a headline.

    In its November 9 update labeled 3 PM EST, N-able said it had no evidence of active exploitation or unauthorized data access. That was the company’s assessment at that point, not proof that every customer environment was clean. A precautionary outage is not, by itself, a disclosure of customer compromise. Nor does it establish when service would safely resume.

    That picture has since changed. N-able’s vulnerability remediation update says N-central 2026.4 HF2 addressed the internet-facing, unauthenticated vulnerabilities, after which it brought its hosted servers back online. It also describes a second publication on November 12 involving Legacy API abuse and Agent impersonation. On November 16, N-able released HF3, which fixes 17 more CVEs, hardens how Agents, Probes and appliances authenticate, and permanently removes the Legacy API. Remote control other than Take Control and the Intune integration remain disabled until a later release. N-able has also said it saw scanning activity tied to the public proof-of-concept code but no indications of compromise within its hosted servers. That statement does not cover customer environments, and The Hacker News has since reported active exploitation of the Legacy API flaws to deploy cryptocurrency miners on vulnerable servers.

    What the Able2Shell Research Establishes

    The name is real: the original Able2Shell write-up uses it. The researcher states that testing used N-central Appliance 2026.4.0.31, a pre-release build. The repository describes an anonymous XML external-entity and session-trust chain leading to code execution, plus stored cross-site-scripting chains that require a ProductAdmin to view attacker-controlled patch details before privileged execution occurs.

    Those are researcher-reported results with different prerequisites, not one universal attack path. The author’s expectation that older versions are affected is not a verified version-by-version assessment. I would not turn it into one. N-able’s precautionary action establishes operational urgency; it does not independently validate every repository claim or demonstrate that attackers used those chains against customers.

    RMM Tool Vulnerability Response Starts With MSP Security Boundaries

    The joint CISA Guide to Securing Remote Access Software, published June 6, 2023 with NSA, FBI, MS-ISAC, and Israel’s National Cyber Directorate, provides a useful baseline. It recommends reduced-privilege RMM configurations for common tasks such as read-only monitoring, multifactor authentication for accounts accessing customer environments, customer separation, and safeguards for mass scripting. These are agency recommendations to implement against your platform’s supported controls, not a promise that every RMM product exposes identical switches.

    My practical review would separate four kinds of authority:

    • Viewing: Who can see inventory and health information without changing a machine?
    • Changing: Who can launch a remote session, deploy software, or run a script across a customer estate?
    • Delegating: Who can create technicians, issue integration credentials, or enable vendor support access?
    • Crossing boundaries: Which accounts and integrations can reach more than one customer?

    Reduce unnecessary authority where the product supports it, and test changes against required maintenance functions. Do not blindly change an agent’s operating-system service identity and call it hardening. Constrain technician roles, automation scope, and network reach deliberately; document exceptions that genuinely require elevated execution.

    Observe the Work, Not Just the Approved Executable

    The CISA-led guide recommends establishing normal behavior, correlating suspicious activity, auditing remote-access tools, and keeping log servers and their alteration or deletion out of RMM tools’ reach. An approved management executable is not an explanation for everything it launches.

    I would correlate endpoint process activity with management audit records: which technician or integration requested the action, which customer and machines it targeted, and whether the work matched an approved change. Unexpected command interpreters, new administrator accounts, unusual remote sessions, or security-setting changes deserve investigation in context. These are behavioral review ideas, not published Able2Shell indicators of compromise.

    Keep a usable copy of the necessary telemetry outside the management plane’s administrative control. If your only record of a suspicious script lives inside the same console that issued it, the investigation has a rather circular dependency.

    Practice an Outage Without Adding Another Uncontrolled Door

    Consider a hypothetical MSP whose patch approvals, device inventory, and customer contact list are accessible only through its RMM console. Disconnecting that console may be the right containment decision, but the team must still identify critical endpoints and reach the people responsible for them. That is an availability failure even if no intrusion occurred.

    My fallback runbook would keep an access-controlled inventory and escalation contacts available independently, identify essential maintenance that can safely wait, and test an approved alternate administration route. That route needs its own authentication, logging, and customer authorization. Installing an ungoverned second remote-control agent everywhere is not a recovery strategy; it is an additional trust relationship.

    For restoration, follow the vendor’s current product-specific remediation instructions, verify the applicable build and configuration, and reconcile accounts, integrations, and queued automation before resuming broad execution. Where there is evidence of intrusion, involve incident responders rather than treating an upgrade as a clean bill of health. Restored console access proves availability, not the integrity of everything previously managed.

    The question I would put into the next exercise is simple: can we stop trusting the management plane without losing the ability to understand and operate the estate? That answer is more useful than another dashboard showing that the dashboard is online.

  • Non-Human Identity Security: Inventory Service Accounts, API Keys, and Bot Tokens

    Non-Human Identity Security: Inventory Service Accounts, API Keys, and Bot Tokens

    Non-human identity security starts with an awkward question: who owns the credentials that keep working after their creator leaves? Service accounts, deployment keys, and bot tokens do not appear on the employee offboarding checklist unless somebody puts them there. I would rather have an inventory that answers that question than a frightening industry ratio and a spreadsheet nobody trusts.

    A Big Ratio Is Not Your Cloud Census

    Entro Labs, the research team inside security vendor Entro Security, reported 144 non-human identities for every human identity in its H1 2025 report. This was vendor-sponsored research using telemetry from Entro’s enterprise customer base, not a representative survey of every cloud estate. Its methodology covers more than 27 million non-human identities across global customers, collected between January 1 and June 30, 2025, spanning cloud providers and SaaS platforms.

    The report does not disclose the number of customer organizations or a detailed counting rule for that ratio. It does not establish that non-human identities outnumber employees in most cloud estates. Human identities are not necessarily employee headcount, either. Treat the finding as a reason to inspect your environment, not a multiplier for estimating its size. More credentials do not automatically mean more risk; their permissions, exposure, and lifecycle matter.

    Make Non-Human Identity Security an Ownership Problem

    Keep the principal separate from its credentials. A service account is an identity; a key or token is a way of authenticating or exercising access. Rotating a credential need not retire the principal, and counting every replacement token as another permanent identity can make your dashboard nonsense.

    AWS’s IAM best practices call for reviewing and removing unused users, roles, permissions, policies, and credentials, applying least privilege, and using temporary credentials with workload roles. Those are AWS-specific controls, not a promise that every SaaS integration supports the same model. My practical inventory would connect these records:

    • Identity and owner: the principal, accountable team, application, environment, and business purpose.
    • Credential references: issuer, key identifier or approved secret-store reference, creation date, expiry where applicable, and revocation procedure. Do not copy secret values into the inventory.
    • Access and trust: allowed actions, target resources, and who or what can assume the identity or obtain a credential.
    • Dependencies and evidence: consuming jobs, last observed use, log coverage, replacement method, and a tested retirement plan.

    Reconcile cloud identity records with deployment configuration, secret-management metadata, and SaaS application registrations. An export from the cloud console is a starting point, not evidence that you found a bot token installed in a separate collaboration service.

    For AWS workloads, prefer IAM roles with temporary credentials where supported. Scope permissions to the required actions and resources, and constrain the trust relationship as carefully as the permissions policy. A narrowly scoped role still needs an appropriately restricted caller. Temporary credentials reduce the lifetime of a stolen credential; they do not make excessive permissions harmless.

    Cloudflare’s Missed Credentials Were Not Harmless

    There is a documented consequence to confusing apparently unused credentials with revoked access. In its disclosure of the November 2023 intrusion, Cloudflare said it had failed to rotate one service token and three service account credentials stolen during the earlier Okta compromise. They were mistakenly believed to be unused. The resulting intrusion reached its Atlassian environment.

    Cloudflare said no customer data or systems were impacted, and described access controls that limited movement. This was not proof that every bot token compromises an entire company. It was evidence that a credential left valid can remain useful to an attacker even after its owner thinks it has no job. An inventory needs an operational revocation state, not just a status someone typed.

    Rotate Without Turning Expiry Into an Outage

    Provider guidance is not interchangeable. Google Cloud’s service account key guidance recommends avoiding user-managed keys where possible, using usage metrics to identify unused keys, and routinely rotating the user-managed keys that remain. It also warns against simply setting key expiry on production workloads because expiry can cause outages; its recommendation there is lifecycle management through rotation. It makes exceptions for some hardware-protected keys.

    AWS’s guidance above takes a different formulation for necessary long-term access keys: update them when needed, using last-used information to make changes safely. Neither page supplies a universal rotation interval for all credentials. Choose a supported authentication mechanism and a lifecycle policy for that mechanism, rather than copying a calendar rule across unrelated services.

    For a planned replacement, my runbook would identify every consumer, deploy the replacement through the approved delivery path, verify successful authentication, and then invalidate the old credential. Where overlapping credentials are supported, keep that overlap controlled and brief. A suspected compromise needs incident handling and prompt containment, not an ordinary change-window delay. Confirm revocation using the issuer’s documented behavior; do not assume replacing a stored key instantly terminates every existing session.

    Test the Inventory Against a Real Dependency

    Imagine a hypothetical deployment bot whose maintainer has left. Ask the owning team to trace its credential reference to the issuer, explain its production permissions, and demonstrate replacement in a safe test environment. Verify the old credential is rejected and the intended job still runs. If ownership or dependencies cannot be established, that is remediation work, not permission to delete blindly.

    I would prioritize unknown owners and broad production access before chasing the smallest possible identity count. Track whether important identities have accountable owners, constrained access, usable logs, and tested revocation. A bigger inventory with those answers can be healthier than a smaller one full of mysteries. The target is controlled access, not winning a ratio contest.

  • OpenSSH Vulnerability Patch for Musl Hosts: How Password-Disabled Accounts Can Be Exploited

    OpenSSH Vulnerability Patch for Musl Hosts: How Password-Disabled Accounts Can Be Exploited

    Portable OpenSSH 10.6p2 landed on Nov. 5, 2026 with a critical security workaround for a password authentication bypass on some Linux systems. The OpenSSH vulnerability patch is small. The operator work is larger: figuring out whether your fleet even runs the risky stack, and what “password-disabled” means in /etc/shadow versus turning password logins off in sshd. A reproducible bypass is not evidence of a verified exploitation wave; the primary sources cited here do not establish a within-hours attack timeline. What they do establish is a sharp, reproducible login path on musl hosts without PAM—and a same-day response plan you can actually run.

    How This OpenSSH Vulnerability Is Exploited—And What to Patch

    Start with the vendor note. The OpenSSH 10.6p2 release notes say the release contains a critical security workaround that affects Linux systems that use musl libc with PAM disabled. Damien Miller’s project text is careful: the team considers the root cause outside sshd, but the condition is exploitable through sshd and can be avoided there. The bug was reported by Özgün Kültekin of Wakefield. Fixed portable builds are labeled 10.6p2; Alpine published its advisory the same day.

    CVE-2026-123158, published Nov. 5, 2026, describes sshd in OpenSSH before 10.6p2 on Linux when musl libc is used without PAM: for some account configurations, an oversized password succeeds. Alpine Linux is named as an example platform. That is not a blanket claim that every OpenSSH daemon on the internet is open. Glibc hosts, OpenBSD, Dropbear, and sshd builds that actually use PAM for password checks sit outside this bypass path.

    The mechanism, as documented on the researcher’s *sshole site and restated in Alpine’s advisory, is an interaction—not classic key authentication “working as designed.” Accounts with * in the shadow password field are supposed to reject every password. Musl’s crypt() can return the string * as an error when a submitted password exceeds its length limit. In the non-PAM path, OpenSSH may borrow a real salt from another account that has a $5$ or $6$ hash so timing does not leak usernames. Hash the oversized password with that salt, get * back, compare it to the target account’s stored *, and the comparison can succeed. Researcher and Alpine guidance put the practical password length window at 257 to 1,024 bytes. Key-based logins are not the bug; confusing a crypt error token with a disabled-account marker is.

    Password-Disabled Is Not PasswordAuthentication No

    Three different account and config states keep getting mashed together in chat threads. Keep them separate on the ticket.

    • Password-disabled (* in shadow): No usable password hash. Common for key-only users and some service accounts. This is the account state the bypass targets when the rest of the stack lines up. Other login restrictions still apply: Alpine notes that the default PermitRootLogin prohibit-password protects root from this password path; an accessible account with passwordless doas can still provide a route to root.
    • PasswordAuthentication no: An sshd setting that refuses password logins entirely. Alpine and the researcher both list it as the immediate mitigation if you cannot patch yet. It is the opposite of “password auth still on,” which is a prerequisite for this path.
    • Locked with !: Alpine’s advisory says accounts whose password field is ! are not susceptible through this * comparison. Historically Alpine also learned that locking with ! can break key logins when PAM is off—which is why some images moved to * and walked into this interaction later. Do not “fix” a fleet by flipping every * to ! without understanding key login side effects.

    Alpine’s Nov. 5, 2026 security advisory is blunt: if you run sshd on Alpine, update openssh and restart sshd; upgrading the package alone does not replace the running daemon. You are in scope when you run the non-PAM openssh-server package (or openssh-server-pam with UsePAM no), PasswordAuthentication is still yes, and an account with a * password field exists alongside at least one account with a usable $5$/$6$ hash. Official cloud images with a default alpine user and passwordless doas raise the stakes after a console password appears elsewhere on the box. Alpine noted that no CVE identifier had been assigned at the time of writing; CVE-2026-123158 carries the same publication date. Prefer the fixed package matrix Alpine published for your release branch over guessing from portable tarball names alone.

    A Same-Day Response Plan for Your SSH Fleet

    The following is my analysis as an operator. Treat the timed drill as hypothetical unless your change board already authorized an emergency window.

    1. Inventory the stack, not just the banner. Ask which hosts run musl (Alpine, OpenWrt, Buildroot, Yocto appliances, some containers that expose sshd) and whether PAM is actually in the password path. A glibc Ubuntu bastion with UsePAM yes is a different work item than an Alpine edge node.
    2. Patch or mitigate in that order. Move affected builds to OpenSSH 10.6p2 or the distro’s fixed package, then restart sshd. If the package lag is real, set PasswordAuthentication no, validate with sshd -t, restart sshd, and verify with sshd -T. Check applicable Match blocks too, using connection-specific sshd -T -C parameters where needed. Keep an existing session and a recovery path available, then test a new authorized connection before closing the change. That mitigation is temporary discipline, not a substitute for the upstream workaround on hosts you intend to leave reachable.
    3. Hunt logs for impossible password successes. The researcher points operators at authentication logs where an account that should never accept a password shows a successful password login. Correlate with shadow: if the field is still *, treat that as a compromise indicator and rotate keys, tokens, and anything that account could reach. Do not invent a global breach rate from a lab reproduction.
    4. Hypothetical same-day drill: Within one change window, list every internet-reachable SSH listener you own, flag musl/non-PAM candidates, push the fixed package or the password-auth kill switch, restart sshd, and sample logs for password accepts on * accounts. That is a tabletop you can schedule—not evidence that honeypots were rooted hours after disclosure.

    What we know from primary notes: Nov. 5, 2026 brought OpenSSH 10.6p2, Alpine packages, CVE-2026-123158, and a clear musl-without-PAM exploit path against password-disabled (*) accounts while password authentication remains enabled. What we do not know from those same sources is a verified “within hours” mass exploitation wave. Patch the hosts that match the prerequisites. Keep the vocabulary honest so the next person on call does not “mitigate” the wrong setting.

  • CISA Flags Exploitation of a Patched Apple Flaw: What the Info-Stealing Research Shows

    CISA Flags Exploitation of a Patched Apple Flaw: What the Info-Stealing Research Shows

    On Nov. 4, 2026, CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog. That federal listing is the clean signal. Separately, security researchers published a report the same calendar day describing a watering-hole campaign that used the patched Apple flaw as one step in mobile info-stealing chains. Operators should keep those layers separate. CISA’s listing means there is evidence of active exploitation meeting KEV criteria. It does not, by itself, verify every payload detail in a vendor report, and it does not invent a fresh zero-day. Apple shipped fixes in May 2024. The practical work for fleets is deciding which Apple products and branches still need the applicable security update.

    CISA Flags Exploitation of a Patched Apple Flaw

    CISA’s Nov. 4 alert says it added one vulnerability to the KEV catalog “based on evidence of active exploitation”: CVE-2024-27834, described as an Apple multiple-products improper authentication issue. The catalog entry summarizes it as a flaw that could allow an attacker with arbitrary read and write capability to bypass pointer authentication. For Federal Civilian Executive Branch agencies, the KEV due date is Nov. 18, 2026. CISA also points agencies to Binding Operational Directive 26-04 on risk-based update prioritization. That directive binds FCEB agencies. CISA encourages other organizations to treat KEV items as high priority; that encouragement is not a private-sector statute.

    Apple’s own notes place a fix for this CVE in May 2024. The iOS 16.7.8 and iPadOS 16.7.8 security content page, released May 13, 2024, lists CVE-2024-27834 under WebKit with the impact line that an attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. Apple credits Manfred Paul working with Trend Micro’s Zero Day Initiative. CISA’s listing concerns exploitation of an Apple flaw patched in 2024, not a brand-new unpatched bug. Other Apple product lines may list the same CVE on their own security-content pages; check the note that matches each device’s OS branch rather than assuming every numerically older build shares the same exposure.

    One technical nuance matters for triage. Apple’s description frames CVE-2024-27834 as a bypass that assumes the attacker already has arbitrary read and write in the process. It is a second-stage primitive, not a lone drive-by by itself. That is why chain reporting matters when deciding how hard to push a short KEV due date.

    What the Info-Stealing Research Shows

    The info-stealing narrative comes from research, not from CISA’s one-line KEV announcement. In a Nov. 4, 2026 post titled Poisoned Source, Sekoia’s Threat Detection and Research team says it uncovered a large-scale watering-hole campaign in mid-October 2026. The report describes three delivery paths: JavaScript injection on compromised legitimate sites, lookalike domains, and a one-week compromise of the Ukrainian Plerdy analytics tracker between Aug. 27 and Sept. 3, 2026. A profiling script then received platform-specific n-day exploit chains without further user interaction, per Sekoia.

    For the Apple PAC issue specifically, Sekoia maps a “Class A” chain aimed at iOS 16.7 that combines CVE-2025-43529 for WebKit remote code execution with CVE-2024-27834 as the Pointer Authentication bypass, then steals cookies. Sekoia also describes heavier iOS 18.5 and Android Chrome chains that collect broader device or Chrome data. Attribution in that report is hedged: “moderate to high confidence” that APT29, or a subgroup, conducted the campaign. That is a researcher assessment. CISA’s KEV alert does not name APT29, does not name Plerdy, and does not describe cookie theft.

    Separate older context from this evidence. Apple documented the CVE-2024-27834 fix in its May 2024 release. Sekoia’s mid-October 2026 discovery and Nov. 4 writeup are the current campaign report that secondary coverage has tied to the KEV addition. Do not flatten 2024 patch history, 2026 watering-hole research, and CISA’s catalog decision into one sentence that claims CISA verified the stealer payload.

    Closing the Gap Between Vendor Fix and Fleet Update

    The following is my analysis as an operator, not a compliance order for private shops.

    1. Inventory Apple endpoints against the security note for each model and OS branch. Use Apple’s applicable security-content page for that product line to see whether CVE-2024-27834 appears and which release addressed it. Prefer current supported updates for that branch over chasing a single ancient minimum across every Apple device you own.
    2. Treat browsing as the exposure path. Sekoia’s model is watering-hole delivery into the browser stack. If a device can open Safari or Chrome on untrusted or third-party-scripted pages, matching the right WebKit or OS update matters more than whether the box is “internet facing” in the server sense.
    3. Prioritize KEV due dates for government fleets, and use them as a benchmark elsewhere. Nov. 18, 2026 is the FCEB due date on the catalog entry. Hypothetical: if you run a mixed civilian contractor shop that mirrors federal phones, aligning those phones to the applicable Apple fix by that date is a defensible change window, not because BOD 26-04 names you, but because the exploit evidence is already public.
    4. Hunt the researcher’s delivery patterns without over-claiming compromise. Look for odd analytics script changes, unexpected third-party JavaScript hosts, and devices whose OS branch still lacks the WebKit fix Apple documents for this CVE. Sekoia reports no persistence, but that does not undo cookie theft. My incident-response recommendation is to review affected sessions and revoke exposed session tokens, rather than treating a reboot as recovery.
    5. Keep the ticket language honest. Write “CISA KEV: CVE-2024-27834, evidence of active exploitation” on one line, and “Sekoia Poisoned Source: reported cookie-stealing chain using CVE-2024-27834” on another. Mixing them into “CISA says APT29 stole cookies” invents a quote CISA did not publish.

    The vendor fix is old. The KEV listing is new. The stealer-chain detail belongs to the researchers who published it. Close the update gap on the Apple builds you still own, and keep the attribution labels as clean as the patch notes.

  • mSecure Password Manager Security Incident: Customer-Shared Notices Describe an Encrypted Cloud Database Copy

    mSecure Password Manager Security Incident: Customer-Shared Notices Describe an Encrypted Cloud Database Copy

    On Nov. 3, 2026, current and former mSecure customers opened an email that told them to protect everything in their vaults and almost nothing about why. The sender was mSeven Software, the company behind the password manager. The subject line was an important security notice. The body used the phrase “suspicious activity,” named no systems, gave no timeline and offered a menu of resets: passwords, two-factor methods, passkeys. For an IT team triaging a password manager incident, that is a difficult starting point. The advice is maximal. The facts are minimal. That gap is the real story of the mSecure password manager security incident, and it is why operators should separate what customer-shared replies attribute to mSeven from what remains unverified.

    What the mSecure Password Manager Security Incident Notice Actually Said

    Customers pasted the Nov. 3 email into mSecure’s own support forum the same day. In a thread titled Important Security Notice Nov 3, 2026, the quoted text reads, in part: “mSeven Software (“mSeven”) recently learned of suspicious activity associated with the mSecure password management application.” It says mSeven launched an investigation, took mitigation steps and hired outside cybersecurity help. Recipients were told they were current or former customers. Then came the reset menu: “This may include changing passwords, resetting or re-enrolling two-factor authentication methods, or removing existing passkeys.”

    That is the entire public substance of the first notice, as customers reproduced it. No count of affected accounts. No list of systems. No statement that vault plaintext was read. No statement that it was not. The company also did not, in that email, say whether Dropbox sync, iCloud, Wi-Fi sync or local-only use mattered. Forum posters asked those questions immediately. For a while, the only answers were more customer posts.

    What Support Later Told Customers

    A clearer paragraph showed up the next day, not as a homepage advisory, but as a paste from support tickets. In the forum thread Update from mSecure Team, a customer named Caitlin published the reply she said she received. According to that reply:

    • mSeven “learned that an unauthorized actor acquired an encrypted copy of a database containing information belonging to current and former users” of mSecure.
    • “mSeven has no evidence that the unauthorized actor has accessed the confidential information stored within the database in the mSecure Cloud.”
    • The company still recommends changing the master password, changing “vital stored passwords,” resetting two-factor methods and replacing passkeys “as a standard best practice.”
    • Deleting the app “will have no impact on this situation.”
    • “This issue only pertains to users that were synching with the mSecure Cloud.”
    • mSeven says it has “no evidence that mSecure is not currently safe for use,” and that it has taken steps “to bolster security.”

    Read that carefully. The customer-shared reply attributes the encrypted-copy claim to mSeven; it is not an independently authenticated public advisory. Decrypted vault contents are not. “No evidence of access” is not the same sentence as “we proved the ciphertext cannot be read.” The company also still has not, in that reply, explained how the copy was taken, what fields sat in the database, whether any keys or verifiers left with it, or how many people got the email.

    What mSecure Says Its Architecture Is Supposed to Do

    mSeven’s published security model is the reason the first email felt so jarring. In mSecure’s Security Model – Secure by design, the company says data is encrypted before it leaves the device, that it uses AES-256, that a locally generated 46-character Account Key “is never stored on our servers,” and that “even we, the creators, have no way to access your information.” It calls that a zero-knowledge model.

    If that model held as described, stealing an encrypted cloud copy should not equal reading every login. That is the architecture’s pitch. It is also why customers asked, reasonably, why the first notice told every current and former user to reset the world. The later Cloud-only caveat narrows the blast radius on paper. It does not answer whether anyone who briefly tried Cloud sync and later switched still has a copy sitting in that database. mSeven’s reply does not say.

    How I Would Triage This, as an Operator

    The following is my opinion, not a vendor playbook.

    1. Treat Cloud sync as in-scope until mSeven publishes otherwise. If you never used mSecure Cloud, the support reply says you are outside this issue. If you did, act as if the encrypted copy exists.
    2. Do not wait for a prettier advisory to rotate the crown jewels. Email accounts, identity providers, banking, domain registrars and anything that can reset everything else come first. Labels like “vital stored passwords” in mSeven’s reply are doing that triage for you without saying the quiet part.
    3. Reset authenticator secrets and passkeys that lived in the vault. The first notice called those out specifically. If mSecure held the TOTP seeds, rotating the site-side 2FA is the point, not just changing the mSecure login.
    4. Change the mSecure master password from a device you trust, then decide whether to stay. Deleting the app, according to the customer-shared reply, does not resolve the incident. Changing the master password also does not retroactively protect an encrypted copy already acquired by an attacker.
    5. Watch for follow-on phishing. Hypothetical: a week from now you get a polished “mSecure breach help desk” message with a password-reset link. That is a standard second act after vague vendor mail. Type the URL yourself.

    I am not saying vault plaintext has been proven stolen. The public record, built from the Nov. 3 email and the later support paste, does not support that claim. I am saying a password manager that emails “reset everything” before it can say “encrypted cloud database copy, Cloud sync only, no evidence of confidential access” has already spent a lot of trust. Operators should spend the next change window on the accounts that matter, document which sync method each vault used, and keep the distinction between ciphertext taken and secrets read in every status update they write for their own users.

  • Synology Says Ransomware Is Hitting NAS Boxes Still Missing a Late-2024 DSM Patch: Finding the Storage Appliances You Haven’t Updated

    Synology Says Ransomware Is Hitting NAS Boxes Still Missing a Late-2024 DSM Patch: Finding the Storage Appliances You Haven’t Updated

    There’s a particular kind of bad news that shows up in a vendor press release and then in your ticket queue the same week: ransomware on the network-attached storage boxes that were supposed to be the backup of last resort. On Oct. 29, 2026, Synology said threat actors are encrypting data on devices still running outdated DiskStation Manager builds, using a vulnerability the company patched in December 2024. Customer reports and a separate technical writeup name the payload C3RB3R. The useful work this week isn’t arguing about ransomware brands. It’s finding every Synology box that still needs a Synology NAS ransomware DSM update, then deciding whether its management page should be reachable from the open internet at all.

    I want the limits of the evidence on the table before the checklist. Synology confirmed the ransomware campaign and pointed to a late-2024 advisory. It has not named a CVE in the Oct. 29 statement, and it has not used the word C3RB3R. The C3RB3R label, the .L0CK3D extension and the read-me3.txt note are documented in Qihoo 360’s analysis. 360 also attributes a different pair of flaws than the advisory Synology linked. Treat those as separate reports from the same period, not proof of a single campaign or one settled root cause.

    What Synology Actually Said

    In its Oct. 29, 2026 notice, Synology wrote: “Synology has identified threat actors exploiting a vulnerability patched in December 2024 to target devices running outdated versions of DSM. These attacks aim to encrypt data and extort ransom.” The company “strongly urges” anyone on vulnerable versions to update immediately and to enable automatic updates. For details it points to Synology-SA-24:20.

    That advisory was first published Nov. 5, 2024, after Pwn2Own. Its critical item is CVE-2024-10441, rated CVSS 9.8: an improper encoding or escaping of output flaw in the system plugin daemon that “allows remote attackers to execute arbitrary code.” The same bulletin also covers CVE-2024-50629 and CVE-2024-10445. Fixed builds listed there include DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7 and 6.2.4-25556-8, or later. Synology’s December 2024 language lines up with the DSM 6.2 fix date in that advisory’s revision history (Dec. 5, 2024). Important caveat: Synology has not confirmed which of those three CVEs, if any specific one, is the entry point in this campaign. “A vulnerability patched in December 2024” is as precise as the vendor got.

    What 360 Reported, and Why It Matters

    On Oct. 30, 2026, Qihoo 360’s anti-ransomware team published an analysis of samples from Synology NAS owners who asked for help during October. 360 identifies the payload as C3RB3R, a Cerber-family variant, and says encrypted files get a .L0CK3D extension (digit zero) with a read-me3.txt ransom note. 360 attributes the intrusion to CVE-2026-13639 and CVE-2026-13684, which Synology fixed on Sept. 18, 2026 in Synology-SA-26:13. Both of those are CVSS 9.8, unauthenticated, and described as letting remote attackers read or write arbitrary files and cause denial of service. Fixed builds on that advisory are DSM 7.4-90075, 7.3.2-86009-4, 7.2.2-72806-9 and 7.2.1-69057-12, or later.

    Those are not the same bugs Synology linked on Oct. 29. I am not picking a winner. For an operator, the practical answer is the boring one: take the newest DSM build your model will accept, because a box patched only to the SA-24:20 floors can still sit below the SA-26:13 floors on the 7.2.1 and 7.2.2 branches.

    Finding the Boxes That Need a Synology NAS Ransomware DSM Update

    The following is my opinion, shaped by Synology’s own hardening guidance and by the version tables above.

    1. Inventory by model and DSM build, not by “it feels current.” Sign in locally, open Control Panel, Update & Restore, DSM Update, and write down the exact build string. Compare it to both advisory floors for that branch. “Latest” in Package Center is not a substitute for reading the build number.
    2. Prefer the newer floor when branches overlap. On DSM 7.2.2, SA-24:20 wants 72806-1 or later; SA-26:13 wants 72806-9 or later. Same story on 7.2.1 (69057-6 versus 69057-12). Aim at the higher number, then take whatever newer release Synology offers for that model.
    3. Turn on automatic DSM updates after you land on a patched build. That is Synology’s explicit recommendation in the Oct. 29 notice. Automatic updates do not undo a compromise that already happened.
    4. Pull DSM off the public internet. Synology’s ransomware prevention article says, plainly, “Do not expose DSM to the Internet unless necessary,” and recommends a VPN when remote access is required. Its broader hardening guide says that if you need to manage DSM remotely, “we recommend connecting via VPN instead of exposing DSM management ports directly to the internet.” Default HTTP and HTTPS ports are 5000 and 5001. In my view, any NAS whose login page answers on a public address is already overdue for a change window, ransomware or not.
    5. Check backups that live on the same chassis. Do not assume backups are safe just because they exist. Check whether local snapshots are protected and whether attached USB copies can be modified by the compromised system; verify an independent offline or off-site recovery copy. Synology also recommends immutable snapshots on supported models. Synology’s own ransomware guidance still points at offline, encrypted backups you can actually restore, following a 3-2-1 pattern, plus rehearsed recovery.

    If You Already See .L0CK3D Files

    Synology’s response checklist starts with isolation: identify affected systems and take them off the network. Preserve the ransom note and logs before you wipe anything. Rotating credentials from a clean machine, not from the suspect NAS, is the order of operations that keeps a second foothold from walking back in. Patching after encryption does not decrypt files. Paying is a separate decision I won’t pretend to settle here; my bias, as an operator, is rebuild from known-good media and restore from offline backups.

    Hypothetical: say you run a dozen Synology units across a few sites, and only three of them still answer on public 5001. Those three are the first change window, even if their DSM builds look fine on paper. Exposure is the correlated failure. The CVE arguments matter for attribution reports. For getting through the week, the build string and the listening ports matter more.

    Update the boxes. Stop advertising the management page. Then go prove the backups restore before the next vendor notice lands on a Saturday.