An unknown ScreenConnect account accessed our machines. What should we do?

November 18, 2026 5 answers
Asked by 7j!florvex_294

We found an account we didn't create in ScreenConnect, and it has accessed some managed machines. Support provided logs but hasn't identified how the account was created. Our admin laptops came back clean in security scans. What should we investigate, and what should we ask support for?

Answers

9x~ferrulejigsaw_618

Treat this as an active security incident, not just a logging problem. Disable the unknown account and contain access through the remote-support system. Consider taking the service offline or removing the agent where needed, but coordinate that with your incident response team so you don't destroy useful evidence or cut off a necessary recovery path.

Isolate the machines the account accessed and bring in incident response help if you don't have the capacity internally. A clean scan on the admin laptops doesn't establish that they weren't used, or that the accessed machines are clean.

Reply to this answer
_u91~florvani.4

Preserve everything you can before making changes. Export the available audit and session logs, save the login alert and its source IP, and record the unknown account's details, including its email, permissions and MFA settings. Note when the account appeared and which endpoints it reached.

Ask support to escalate this as a security incident and provide account creation, authentication, administrative and session audit records for the relevant period. Ask them to confirm what events are logged, how long they're retained, and whether the missing creation event is unavailable or simply not included in what they sent. That distinction matters.

n.426~quorlavi:

Also note whether the instance is hosted or self-hosted, and whether it's integrated with another management system. That could change which logs are available.

Reply to this answer
c.714!plumferrule

Start with the endpoints the account actually accessed. Look for unexpected local accounts, changes to administrator groups, suspicious files and other remote-management tools. Check directory accounts and privileged group membership too. The ScreenConnect account may be only one part of the incident.

Reply to this answer
_m28~velnixa.7

Check the deployment and patch level, especially if you run the server yourself. Review the vendor's security bulletins and update the server and clients as applicable. Don't assume a vulnerability was the entry point, though. An existing admin session, an integration or another management account also deserves investigation.

Reply to this answer
Vexdali.9w

Once the immediate incident is contained, take a hard look at whether the product gives you enough audit visibility. A remote-control tool with unexplained account creation and no usable trail is a serious problem. That could be a reason to replace it, but switching products won't by itself tell you what happened on the machines already accessed.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions