Detect Motex LANSCOPE Endpoint Manager - Improper Verification of Communication Channel Source (CVE-2025-61932) in Google Chronicle
CVE-2025-61932 is an Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Motex LANSCOPE Endpoint Manager. This flaw allows an attacker to send commands or data through a communication channel without proper verification of the channel's origin, potentially enabling unauthorized control over managed endpoints. The vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild. Attackers may abuse this to impersonate the LANSCOPE management server and push malicious instructions to endpoint agents.
MITRE ATT&CK
- Tactic
- Initial Access Lateral Movement Impact
YARA-L Detection Query
rule cve_2025_61932_lanscope_suspicious_comms {
meta:
author = "df00tech Detection Engineering"
description = "Detects LANSCOPE Endpoint Manager agent communicating with potentially unauthorized management channels - CVE-2025-61932"
severity = "HIGH"
priority = "HIGH"
reference = "https://nvd.nist.gov/vuln/detail/CVE-2025-61932"
events:
$network.metadata.event_type = "NETWORK_CONNECTION"
(
re.regex($network.principal.process.file.full_path, `(?i)(lanscope|lsepagent|epagent|lsep)`) or
re.regex($network.principal.process.file.names, `(?i)(lanscope|lsepagent|epagent)`)
)
$network.target.port in (80, 443, 8080, 8443)
$network.principal.hostname = $hostname
$network.target.ip = $dest_ip
match:
$hostname, $dest_ip over 1h
outcome:
$risk_score = max(65)
$process_path = array_distinct($network.principal.process.file.full_path)
$dest_ports = array_distinct($network.target.port)
condition:
#network >= 3
}Chronicle YARA-L rule detecting repeated LANSCOPE agent network connections that may indicate exploitation of CVE-2025-61932 through rogue management server impersonation.
Data Sources
Required Tables
False Positives & Tuning
- High-frequency legitimate polling by LANSCOPE agents against authorized management servers
- LANSCOPE update mechanisms triggering multiple connections during software updates
- Chronicle UDM field mapping inconsistencies for non-Windows LANSCOPE deployments
- Multi-tenant environments where agents legitimately connect to shared infrastructure
Other platforms for CVE-2025-61932
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate LANSCOPE Agent Connection to Rogue Management Server
Expected signal: DeviceNetworkEvents showing outbound connection to 192.0.2.100:8443 from powershell.exe; Sysmon Event ID 3 network connection; Windows Firewall log entry for outbound blocked/allowed connection
- Test 2LANSCOPE Agent Configuration Tampering via Registry
Expected signal: Sysmon Event ID 13 (Registry value set) for HKCU\SOFTWARE\TestLANSCOPE keys; Windows Security Event ID 4657 (registry value modified) if audit registry is enabled; EDR registry modification alert
- Test 3DNS Query to Suspicious LANSCOPE Management Domain
Expected signal: DNS query logs showing resolution attempt for test-mgmt.example-lab.local; network connection attempt to port 8080; process execution logs showing nslookup/dig/curl invocation; endpoint network telemetry from EDR
Unlock Pro Content
Get the full detection package for CVE-2025-61932 including response playbook, investigation guide, and atomic red team tests.