🧭 Decision Radar
Relevance for Algeria
High
▾
Infrastructure Ready?
Yes
▾
/usr/bin/dbus-authd and TCP port 19800 activity, and rebuilding appliances from clean images use standard administration capabilities.
Skills Available?
Partial
▾
Action Timeline
Immediate
▾
Enterprise security operations teams, managed service providers, banking and telecom infrastructure administrators, public-sector helpdesk operators
Decision Type
Operational
▾
Quick Take: If your organisation runs self-hosted BeyondTrust Remote Support versions 26.2.3 or earlier, apply patch BT26-05-RS immediately—and if you cannot rule out prior intrusion (especially given that attackers deleted local logs and set up /usr/bin/dbus-authd root persistence and TCP port 19800 tunnelling), follow Mandiant’s advice and rebuild from a clean, patched image. Just as importantly, review your security monitoring pipeline to ensure third-party triage tools cannot auto-close privilege-escalation alerts as false positives.
Six Weeks of Zero-Day Exploitation and a Dismissed Alert
A critical vulnerability in BeyondTrust Remote Support was actively exploited for weeks before its public disclosure. According to Rescana, CVE-2026-102764 is a critical flaw in BeyondTrust Remote Support, rated CVSS 4.0 at 9.3 by BeyondTrust (CNA) and 9.8 under CVSS 3.1 by NVD. Cybersecurity News reports that the flaw was exploited as a zero-day in late August 2026, before BeyondTrust disclosed it on October 15.
Specifically, GBHackers notes that BeyondTrust says the first attack came on 29 August 2026 and hit one BeyondTrust-hosted Remote Support instance and one self-hosted appliance, while no customer count was given. Most strikingly, the intrusion did not go unspotted by endpoint telemetry: according to GBHackers, BeyondTrust’s sensors alerted on the privilege escalation, but a third-party triage tool closed those alerts as false positives.
Attribution points to an experienced espionage operator. According to Cybersecurity News, Google’s Mandiant links the activity to ARMORY CASTLE, a suspected China-nexus group previously tracked as UNC5221. GBHackers further reports that Google warns the group has previously shifted from selective zero-day exploitation to broader opportunistic attacks once vulnerabilities became public.
Root Persistence, Log Deletion and Patching Deadlines
Forensic findings from Mandiant detail how the intruders entrenched themselves once inside an appliance. Cybersecurity News reports that attackers escalated to root by copying /bin/sh to /usr/bin/dbus-authd with SUID set, and deployed a SAWFLY webshell and a BARECLAW SOCKS5 tunneler on TCP port 19800. To hinder incident responders, Mandiant also found the attackers deleted logs across system, web server and application locations to hide their tracks.
According to an advisory from the Canadian Centre for Cyber Security, affected are Remote Support versions 26.2.3 and earlier; self-hosted customers need the BT26-05-RS patch, while SaaS customers were patched as of October 9, 2026. Rescana notes that CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on 16 October 2026 with a federal due date of 19 October.
Crucially, applying the update is only the first step. Cybersecurity News reports that Mandiant warns that patching closes the flaw but does not remove evidence of earlier compromise, and recommends rebuilding from a clean, patched image if compromise cannot be ruled out.
Advertisement
What This Means for Enterprise Administrators and Managed Service Providers
While the cited reports do not identify specific victims by country, remote-support appliances are widely deployed by enterprise helpdesks and managed service providers in Algeria and across North Africa to administer internal and client machines. Because ARMORY CASTLE has previously shifted from selective zero-day exploitation to broader opportunistic attacks after vulnerabilities became public, self-hosted installs face immediate risk. Three operational actions follow directly from the disclosures.
1. Apply patch BT26-05-RS immediately—and rebuild if prior compromise cannot be ruled out
Any organisation running self-hosted BeyondTrust Remote Support versions 26.2.3 and earlier must apply patch BT26-05-RS without delay. However, because attackers escalated to root via /usr/bin/dbus-authd with SUID set, deployed the SAWFLY webshell and BARECLAW SOCKS5 tunneler on TCP port 19800, and deleted system, web server and application logs, Mandiant recommends rebuilding from a clean, patched image whenever compromise cannot be ruled out.
2. Never allow an automated triage tool to auto-close privilege escalation alerts on critical appliances
BeyondTrust’s own sensors detected the privilege escalation, yet a third-party triage tool closed those alerts as false positives, allowing the activity that began on 29 August 2026 to persist until October. Security teams using external alert-triage tools or outsourced monitoring must forbid automatic dismissal of root-escalation alerts on remote-support and boundary appliances.
3. Ship appliance logs to an external, append-only collector in real time
Mandiant found log deletion across system, web server and application locations on compromised systems. If logs remain only on the local appliance, an attacker who gains root access can erase evidence of intrusion—making it impossible to rule out compromise without a full rebuild.
The Structural Lesson
Remote-support platforms sit at the top of the administrative trust chain: compromising one appliance gives an attacker a bridge into the endpoints and networks it supports. The CVE-2026-102764 incident shows that detection sensors are only as effective as the triage layer sitting behind them. When a third-party triage tool silences a real privilege-escalation alert as a false positive, a well-instrumented environment behaves no differently from an unmonitored one.
For enterprise security teams in Algeria, the takeaway combines immediate hygiene on Remote Support versions 26.2.3 and earlier with a broader governance rule: human analysts—not automated suppression rules—must review every privilege-escalation alert on administrative appliances.
Frequently Asked Questions
What is CVE-2026-102764 and which BeyondTrust versions are affected?
CVE-2026-102764 is a critical vulnerability in BeyondTrust Remote Support rated CVSS 4.0 at 9.3 by BeyondTrust (CNA) and 9.8 under CVSS 3.1 by NVD. It affects Remote Support versions 26.2.3 and earlier; SaaS customers were patched as of October 9, 2026, while self-hosted customers must apply the BT26-05-RS patch.
Why did the August 29 attack go undetected for so long?
According to GBHackers, the first attack occurred on 29 August 2026—hitting one BeyondTrust-hosted instance and one self-hosted appliance—and BeyondTrust’s sensors did alert on the privilege escalation. However, a third-party triage tool closed those alerts as false positives, and attackers also deleted logs across system, web server and application locations.
Who is behind the exploitation and why does Mandiant recommend rebuilding appliances?
Google’s Mandiant links the activity to ARMORY CASTLE, a suspected China-nexus group previously tracked as UNC5221, which deployed a SAWFLY webshell, a BARECLAW SOCKS5 tunneler on TCP port 19800, and a SUID root copy of /bin/sh at /usr/bin/dbus-authd. Because patching closes the vulnerability but does not remove prior backdoors or restore deleted logs, Mandiant recommends rebuilding from a clean, patched image if compromise cannot be ruled out.
Sources & Further Reading
- BeyondTrust zero-day exploited by China-linked ARMORY CASTLE group — Cybersecurity News
- BeyondTrust zero-day alerts were closed as false positives by third-party triage tool — GBHackers
- Google warns ARMORY CASTLE may expand BeyondTrust zero-day attacks — GBHackers
- AL26-025: Critical vulnerability impacting BeyondTrust Remote Support (CVE-2026-102764) — Canadian Centre for Cyber Security
- BeyondTrust Remote Support CVE-2026-102764 added to CISA KEV — Rescana













