Threat Intel
Browser‑in‑the‑Browser Phishing Enables Rogue ScreenConnect Persistence
Attackers used a phishing campaign that delivered a browser‑in‑the‑browser (BIB) page, enabling installation of a rogue ScreenConnect remote‑management module that persisted on victim endpoints. The technique bypassed standard endpoint detection and allowed stealthy lateral movement. Defenders should block BIB URLs, audit ScreenConnect processes, and enforce MFA on RMM tools.
What Happened
Cybercriminals sent targeted phishing emails that, when opened, loaded a browser‑in‑the‑browser (BIB) page. The BIB page executed JavaScript that installed a rogue ScreenConnect module on the victim’s machine. The module created a persistent service that allowed attackers to maintain remote access and evade detection.
Impact
Endpoints running any version of ScreenConnect were compromised. The rogue module persisted across reboots, enabled stealthy lateral movement, and could exfiltrate data without triggering typical endpoint alerts. Organizations with unmanaged or poorly secured RMM deployments were most at risk.
What to Do
- Block known BIB URLs and any suspicious email attachments or links.
- Audit all ScreenConnect processes; terminate any unknown or unauthorized instances.
- Enforce multi‑factor authentication for all RMM accounts and restrict remote‑access permissions.
- Apply the latest ScreenConnect patches and consider disabling legacy remote‑access features.
- Monitor for anomalous network traffic originating from ScreenConnect ports and services.