The FBI describes FaceStealer as a social-engineering scheme using fake video meetings to infect devices. In November 2026, the FBI and DOJ announced disruption of its cloud infrastructure. The risk extends beyond the meeting: a victim’s access and trusted relationships can be reused to approach other people.
An invitation from a hijacked account
According to the FBI, attackers reuse compromised communication accounts and secretly recorded victim videos. Cryptocurrency and Web3 professionals are among the targets.
A familiar appearance on screen therefore cannot authenticate a request. The scheme can exploit a real relationship without the impersonated person taking part in the call.
Fake troubleshooting triggers infection
BleepingComputer describes technical-problem pretexts leading to a supposed update or installer. Open-source developers are also targeted for their access to software repositories.
The decision point is practical: a conversation should not become permission to execute an unknown program. Do not paste a command offered as a fix for sound or camera problems.
Verify the meeting separately
Cloud Security Alliance emphasizes the importance of stolen genuine video in this chain. Looking only for visual defects in an AI deepfake misses part of the risk.
Call the contact through a number you already have, or confirm in a separate established conversation. Then join through the official meeting app instead of following the troubleshooting workflow you received.
Prepare a response after exposure
If an employee executed the fake fix, involve support before reconnecting sensitive accounts. Preserve the invitation link, messages and timestamps to help the investigation.
The CSA note recommends considering persistent access and copied secrets. After examining the device, the team should review messaging sessions and repository or wallet access used on it.
The connection with Soclyde
Soclyde keeps passwords in an encrypted vault on your devices. Distinct secrets prevent one reused password from opening several accounts during replacement after an incident.
A local vault does not make an infected device trustworthy. Device checks, session revocation inside each service and caller verification remain necessary.
What to remember
When unexpected troubleshooting appears in a video meeting, pause the installation and verify through another channel. If investigation requires replacing a secret, prepare it from a clean device with the Soclyde generator.



