CVE-2026-102764
Domains:
64[.]128, 65[.]75
Get tomorrow's brief in your inbox
October 17, 2026: Patch self-hosted BeyondTrust Remote Support and investigate exposed appliances. Huntress's October 16 snapshot documents unauthorized ConnectWise application sign-ins in 162 tenants. Review application credentials, affected developer packages, and legacy Windows authentication alongside patching.
BeyondTrust Remote Support: patch and assess exposure
BeyondTrust's October 15 advisory rates CVE-2026-102764 critical, CVSS 4.0 score 9.3, affecting Remote Support through 26.2.3. Apply BT26-05-RS; versions older than 24.3.1 need an upgrade before the patch. The advisory says SaaS customers were patched by October 9. [1] BeyondTrust reports exploitation beginning August 29 and attributes the activity to ARMORY CASTLE. [2]
ConnectWise application credentials: investigate tenant access
Huntress's October 16, 19:00 UTC snapshot confirms unauthorized sign-ins in 162 Microsoft 365 tenants using a ConnectWise Cloud Backup credential. The documented first sign-in window is October 15, 06:13-08:34 UTC. The same primary report describes a separate application adding Global Administrator and credentials to other applications in one tenant. These observations require investigation; do not assume all activity has one established operator. [3]
Preapprove crisis providers and payment controls
Correlate indicators with behavior
144.172.64[.]128 in the documented unauthorized application sign-ins. [3] Correlate it with application identity, token activity, role changes, and credential additions; a network block does not establish tenant recovery.104.234.65[.]75:700 serving a stealer/RAT in its October 13 analysis. Its recovered banner.png chain led there, but it did not recover the native loader's banner.jpg and did not confirm an identical payload for that path. [4] Treat the address as an investigation lead, with that limitation recorded.AOMEI distribution tampering calls for historical review
GTIG and Mandiant's October 15 analysis describes UNC7017 tampering with AOMEI update configuration during April-July 2026. Individual malicious windows lasted five to ten minutes and delivered CROSSROAD and SHINYROAD. The investigators say AOMEI reported corrective action on its distribution servers. [5]
MALFEX uses a native npm loader
SafeDep's October 13 original analysis documents imgdecode versions 1.0.0-1.0.3, including an import-triggered native addon in later versions. The observed loader retrieves encrypted content and injects into dllhost.exe; an installation script is not required. [4]
Include facilities in continuity planning
October authentication hardening: use the correct registry value
Microsoft says the October 13 security update changes the internal default for an unset BlockNtlmv1SSO value from Audit to Enforce. On affected devices with Credential Guard disabled and the value unset, generation of NTLMv1-derived single-sign-on credentials is blocked; MS-CHAPv2-based Wi-Fi, Ethernet, or VPN connections can be affected. [6]
CaptiveCrunch: reject software updates from portal pages
SentinelOne's October 16 account attributes CaptiveCrunch to APT29 and describes observed link-local LLMNR spoofing that led Windows connectivity checks to attacker-controlled lures. In its observed cases, users manually downloaded and launched browser-themed files. [7]
BlockNtlmv1SSO in any approved configuration change. [6]OpenBSD fixes include both reliability and security errata
OpenBSD's official 7.9 errata lists 018, dated September 14, as a shmat integer-overflow reliability fix and 026, dated September 30, as a kernel reference-counting use-after-free security fix. [8]
Prioritize patch verification, historical telemetry, application-credential review, and recovery evidence together. An updated appliance, disabled application, or clean download response answers only part of an incident investigation.
[1] BeyondTrust BT26-05 advisory, October 15
[2] BeyondTrust ARMORY CASTLE incident account, October 15
[3] Huntress investigation, original October 16 snapshot
[4] SafeDep original MALFEX analysis, October 13
[5] Google Threat Intelligence and Mandiant AOMEI analysis, October 15
[6] Microsoft KB5066470, NTLMv1 changes and October 13 enforcement