How should we investigate Windows PCs after the Optimizely compromise?

November 21, 2026 5 answers
Asked by _c92!vexmari.5

Several school PCs started behaving strangely around the time of the Optimizely compromise. Some screens went black while the machines stayed on, and an enumeration alert appeared for one device. The affected PCs are now powered off.

Reported guidance seemed focused on iOS, so I'm not sure what evidence would point to a Windows infection or how to investigate without assuming the events are connected. Where should we start?

Answers

_h56!plovrano.8

Start with a timeline, not the assumption that Optimizely caused it. Line up the enumeration alert, firewall changes, screen failures, network logs and any endpoint events. Check whether the affected machines share a subnet, power circuit, software or configuration.

Lots of established connections can be normal, and black screens with unresponsive input don't establish malware on their own. For the connections you recorded, identify the owning processes and destinations where possible. Then look for unusual process launches, logons, scheduled tasks and services around the same time.

_c92!vexmari.5:

The machines stayed powered on and connected, but the displays were black and local input wasn't responding. I'll include the firewall changes in the timeline.

Reply to this answer
8k!gasketpocket_391

Keep the powered off machines untouched for now if you may need forensic evidence. Preserve the alert details and relevant endpoint, network and authentication logs before they roll over. Coordinate any collection or rebooting with whoever is handling the investigation.

If compromise becomes likely, scope beyond that row of PCs. Check for suspicious authentication and activity involving other systems or accounts, not just a clean antivirus scan on the affected endpoints. Legitimate system tools can be abused, so process context matters.

Reply to this answer
Veldruni+4t

For recovery, find the earliest evidence of malicious activity before deciding which backups to trust. A backup from before the symptoms is a starting point, not proof it's clean. If logs show earlier access, look further back.

Rebuild affected machines from trusted images if the investigation warrants it, and scan data before restoring it. Keep evidence separate from the systems you're putting back into service.

Reply to this answer
_f63+quorlavo.2

I'd tighten outbound access from endpoints as a separate hardening task. Allowing only the traffic they actually need can reduce exposure, though blocking everything except web traffic may break school services. Test and document the rules, especially since firewall changes are already part of the timeline.

Reply to this answer
4c~gobletpulley_692

Some people would rebuild every Windows machine immediately, but the symptoms described don't yet establish how far an incident extends or even whether this is an infection. Treat it seriously while collecting enough evidence to make that decision. A negative virus scan doesn't settle it either.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions