IT support ransomware attack response starts with an ordinary call that may be anything but ordinary. On November 18, 2026, Ukraine’s Cyber Police described a case in which an impostor kept an employee on the phone while an accomplice entered corporate systems. The police said the wider investigation identified at least 28 companies that had paid more than $40.5 million in ransom.
The account gives defenders a practical sequence to test: validate the call, contain access, scope the intrusion, and protect recovery. The police reported four key suspects in custody and said the investigation of other participants continues. Their statement does not say the entire network has been dismantled.
IT Support Ransomware Attack: What Did Police Document?
According to Ukraine’s Cyber Police, the group researched a target’s finances, employees, assets, and system weaknesses before contact. Its operators then used a platform with AI-generated voice messages and posed as IT support. They persuaded employees to disclose credentials or install remote access software, giving them entry to corporate networks.
Once inside, the attackers stole confidential information and encrypted files, police said. They demanded payment for decryption while threatening to release the stolen data. That combination can leave an organization facing both an operational outage and an exposure decision.
- 1Impostor EmployeeClaims to be IT support using AI-generated voice messages
- 2Employee Corporate networkDiscloses credentials or installs remote access software
- 3Impostor Corporate networkSteals information and encrypts files
The sequence above paraphrases the police account; it is not a description of every incident. The police identified targets in oil and gas, pharmaceuticals, manufacturing, logistics, finance, and critical infrastructure. A vishing response guide helps explain why a familiar support story still needs independent verification.
- At least 28Companies identified as having made ransom paymentsSource: Ukraine Cyber Police, November 18, 2026
- More than $40.5mRansom paid by those companiesSource: Ukraine Cyber Police, November 18, 2026
- 66Coordinated searches in Kyiv and 11 Ukrainian regionsSource: Ukraine Cyber Police, November 18, 2026
Which Access Should the Team Check First?
Start with the named employee’s account and device, then expand only as the evidence warrants. Review identity provider sign-in logs for new sessions, unusual locations, and changes around the call time. Record the exact time of the call, the claimed support purpose, and who approved any remote session.
Check endpoint management and software inventory for newly installed remote access applications. Examine session records and network connection logs for the affected device, then compare them with authorized help desk tickets. This is a defender workflow derived from the reported entry path, not a police finding about a specific tool.
Brandefense Blackhole recorded five dark-chat posts matching the broad term “IT support ransomware” from August 21 through November 19, 2026. The measured unit is matching posts, and the count is not a tally of incidents or actors. It does not connect those posts to the Ukrainian investigation.
A ransomware intelligence review belongs beside internal access evidence when teams assess external risk. For this case, the police statement supplies the confirmed operation details. Any unrelated chatter remains a lead for separate verification.
What Should Responders Do in Order?
The order below aims to preserve evidence while stopping unauthorized access. Keep incident leadership and legal counsel involved when stolen data or extortion may be present. The police statement describes the attack, while these operational steps are our recommendations.
- Verify the callAsk the employee to end the conversation. Contact the help desk through an independently known channel and preserve the ticket and call time.
- Contain the identityIn the identity provider console, disable the affected account, revoke active sessions, and reset credentials through a trusted process.
- Contain remote accessIn endpoint management, identify the installed remote access application and terminate unauthorized sessions. Preserve logs before removing software.
- Scope lateral activityCompare identity sign-in, endpoint, and network logs from the call onward. List other accounts, devices, and data stores the session reached.
- Protect recoveryCheck backup console access, recent job failures, and restore points. Isolate recovery credentials and test restoration on clean systems.
- Coordinate decisionsRecord evidence of data access and encryption separately. Escalate extortion communications, disclosure duties, and recovery choices to the incident team.
Why this order? Independent call verification can stop a live social engineering attempt. Identity and remote session containment narrow the attacker’s access, while preserved logs support later scoping. Backup validation then gives the recovery team a dependable starting point.
Do not treat a password reset alone as closure if remote access software remains active. Likewise, a clean device does not answer whether data was copied. The police described theft and encryption as separate pressure points, so the incident record should track both.
How Should Teams Prepare Before the Next Call?
Give employees one official method to verify support requests, including calls claiming an urgent device problem. Require a ticket and a callback through a known number before installing remote tools or sharing credentials. Help desk teams should log approved remote sessions and alert on installations outside that process.
Run a tabletop exercise that starts with a caller who sounds credible and ends with suspected remote access. Ask who can revoke sessions, isolate a device, preserve logs, and authorize recovery. The ransomware readiness workflow offers a related planning context for those decisions.
The police say four key suspects are in custody, while investigators continue identifying other participants. Some members of a wider associated network were former Conti participants, according to the statement. That history does not identify this operation as Conti, and it does not change the immediate response sequence.
Frequently Asked Questions
Does this police statement mean every suspect has been arrested?
No. Police said four key suspects are in custody and that investigators continue identifying other participants.
What should an employee do during an unexpected IT support call?
End the call and contact the help desk through a known channel. Do not disclose credentials or install remote access software based only on the caller’s request.
