Skip to content
nulltapE-reader edition

← All e-reader articles

5 min read

Cisco Talos Traces Quick Assist Call Into VYPR Ransomware

A vishing call opened a Quick Assist session in a Talos case. The intruder moved through existing remote-management software, stole data and disabled endpoint defenses.

Read on the standard site

Generated depiction of a telephone beside an office laptop with its screen blurred, illustrating a support call before remote access.

A user accepted a Microsoft Quick Assist session during a voice-phishing call. In the Q3 2026 case described by Cisco Talos Incident Response, the intruder then used existing remote-management software, exfiltrated data over multiple days, disabled endpoint protections and ran VYPR ransomware. For a Windows fleet, the first question is whether an unexpected support session gave someone interactive access before the endpoint alerts began.

Talos saw phishing in 37% of its incident-response engagements and ransomware or pre-ransomware in 27% during the quarter. Those are shares of the cases Talos handled, rather than rates across all organizations. The VYPR case shows how an ordinary remote-help workflow can become the first step of an intrusion; Talos says the precise pretext used on that call was unconfirmed. In other Q3 cases, actors impersonated IT help desks and talked users into granting access through legitimate remote tools.

A support session opens access

Microsoft’s Quick Assist documentation explains why the call can work. A helper signs in with a Microsoft account or Microsoft Entra ID, gives a time-limited code to the user and asks the user to allow screen sharing. The helper can then request control, which the user approves separately. The person sharing the device does not authenticate to Quick Assist. The helper generally operates with that user’s device permissions; some actions still need the user to respond to a Windows permission prompt. A convincing caller can walk the user through those prompts in real time.

Talos puts the entry point plainly: “The actor gained initial access through voice phishing (vishing); they tricked a user into initiating a Microsoft Quick Assist session, allowing remote access to the endpoint.” This was a user-initiated connection to a real Microsoft service, so treating every Quick Assist launch as malicious would bury the sessions responders need to examine. Ask the user whether they called the approved support desk first, then correlate the session time with activity on that workstation. Microsoft advises users to start the contact themselves by calling their support staff directly.

Existing RMM carried the intrusion

After the Quick Assist entry, the actor used remote monitoring and management software already present in the environment. Talos says that software subsequently executed PowerShell activity to download and install an MSI package from a remote IP address. Talos also observed MeshAgent, Rclone, PsExec, an IP scanner and Microsoft Terminal Services Client (MSTSC) during the attack. These tool names are investigation leads; legitimate administrators use remote-access and administration software too. Look for their use on the same endpoint after the unexpected session, under the same user or newly obtained accounts.

Talos observed data leaving over multiple days before encryption. The operator tested different exfiltration parameters and deployed several vulnerable drivers to disable EDR and antivirus. Bringing a vulnerable driver onto a Windows host can give an intruder kernel-level access to interfere with security software. Talos assessed VYPR as relatively new and operationally immature: its operators took unusually long to exfiltrate and encrypt data, and their data-leak site appeared after the engagement. The long dwell time in this case gave responders a wider interval of remote-tool, transfer and driver activity to reconstruct.

The report also describes Interlock operators trying to uninstall Cisco Secure Endpoint, terminating cscm.exe and sfc.exe with PsExec.exe and taskkill.exe, switching off Windows Defender real-time protection, and clearing event logs. Those observations belong to a different ransomware case; they show why a local log gap or a silent security agent needs off-device evidence before an investigator decides what happened.

Keep support access on a leash

For an organization that supports users through another approved tool, Microsoft recommends removing or disabling Quick Assist. On managed Windows devices, the Microsoft guidance lists Settings → Apps → Installed apps → Quick Assist → Uninstall as one removal path. Confirm it is absent on a representative managed endpoint and try the shortcut Ctrl+Windows+Q to verify the retired workflow cannot launch. Retain a documented route for users to contact the real help desk. Where the organization uses Quick Assist, require a ticket and a user-initiated call-back through its published support number before approving a session.

Microsoft says blocking the Quick Assist primary service at https://remoteassistance.support.services.microsoft.com also disrupts Intune Remote Help. If Remote Help is the approved replacement, use the application-removal route and check the support workflow before changing the shared network endpoint. Microsoft recommends Remote Help for single-tenant environments that need role-based helper access, Conditional Access and session logs. Quick Assist itself creates no session logs on the helper’s or sharer’s device, according to Microsoft; its service keeps limited session-health data. Preserve your own endpoint, identity, RMM and network telemetry for an investigation.

Talos found insufficient logging in more than 40% of its Q3 engagements. It recommends forwarding workstation, server, network, cloud-identity and security-appliance logs to centralized storage with at least 90 days of retention, with process creation and command-line auditing enabled. For the VYPR path, correlate an unrequested support session with RMM activity, MSI installation, subsequent transfer-tool use, new driver installation and changes in EDR health. Treat confirmed unauthorized control as an incident and preserve centrally stored events before reimaging the workstation. Local event-log clearing should leave a trace in the forwarded stream if forwarding and retention worked.

Verify the support path

If the help desk uses a different support tool, remove Quick Assist from managed endpoints and verify the approved support route still works. If it uses Quick Assist, make user-initiated contact and a ticket the condition for granting control. Forward endpoint and RMM activity off-device, then test one workstation by generating a harmless process-creation event and checking that the event reaches central storage with its timestamp and host identity. That retained record is what lets an investigator follow a suspicious help session into subsequent remote access, even when an intruder clears local logs.

Primary sources