What happened
SCKit worm installs hidden ScreenConnect clients, captures session cookies, and relays them to a C2 server across hundreds of compromised endpoints.
Why it matters for trust and compliance
- The incident underscores the importance of controlling third‑party remote‑access tools and maintaining continuous, auditable logs of their usage.
- Map remote‑access tool governance to your audit framework and collect continuous evidence of authorized usage.
- Use continuous monitoring to detect unauthorized client installations and anomalous cookie‑relay traffic.
Who is affected
Enterprises using remote‑support platforms (ScreenConnect/ConnectWise Control) Managed Service Providers and SaaS vendors
Recommended actions
- Inventory all remote‑access tools and enforce strict configuration baselines.
- Deploy endpoint telemetry to log client installations and session‑cookie activity.
- Conduct a focused threat‑hunt for SCKit IoCs and rogue ScreenConnect binaries.