Quick Takeaways
-
Attackers are brute-forcing internet-exposed Microsoft SQL Server systems using more than 2,700 passwords, with a scanner checking for open port 1433.
-
After gaining access, they exploit T-SQL and
xp_cmdshellto run Windows commands, install malware, and create disguised scheduled tasks for persistence. -
The payloads include a Monero miner and Gh0st RAT: the miner consumes server resources, while the RAT enables remote control, keylogging, data theft, and other actions.
- Reduce exposure and detect compromise: keep SQL Server behind a firewall or VPN, block external port 1433, use strong unique passwords, disable
xp_cmdshellwhen unnecessary, and monitor for suspicious tasks, files, and CPU spikes.
The Core Issue
Since at least early October 2026, unidentified attackers have targeted Microsoft SQL Server systems exposed to the internet. They scan for servers with port 1433 open, then use a tool to test more than 2,700 passwords against accounts such as “sa” and “admin.” When a password works, they exploit SQL Server commands to install malware. The campaign succeeds largely because some servers are exposed and protected by weak or reused passwords.
The affected systems face two threats: a Monero miner that consumes computing power, and Gh0st RAT, which gives attackers remote control and can support data theft. The malware also creates disguised scheduled tasks to persist on infected machines. Fortinet’s FortiGuard Labs identified the campaign and detailed its infection chain in a report published November 12, 2026; analyst Xiaopeng Zhang described how the attackers abuse T-SQL to run commands on compromised servers.
Critical Concerns
This attack could affect any business with an internet-exposed Microsoft SQL Server, especially where passwords are weak, reused, or unprotected by multifactor authentication. Attackers can try large sets of stolen or common passwords, gain access, and install remote-access malware. Once inside, they may steal sensitive data, disrupt systems, or use the server as a foothold for further attacks. Consequently, a business could face costly downtime, recovery and legal expenses, regulatory penalties, and lost customer trust. Even a small company can suffer lasting damage. Regular patching, strong unique passwords, restricted server access, and monitored backups reduce the risk.
Possible Remediation Steps
Rapid remediation limits an intruder’s opportunity to establish persistence, steal data, or expand access.
Mitigation and Recovery
- Contain affected servers: Isolate suspected systems from the network while preserving logs and other evidence for investigation.
- Block unauthorized SQL access: Restrict SQL Server exposure to trusted networks or approved hosts; disable unnecessary public access and services.
- Secure accounts: Disable compromised or unused accounts, reset affected passwords, and require long, unique credentials and multifactor authentication where supported.
- Remove malware and persistence: Use trusted security tools to investigate remote-access malware, scheduled tasks, unauthorized services, and other changes; rebuild systems if integrity cannot be verified.
- Patch and harden: Apply current SQL Server, operating-system, and security updates; enforce least privilege and review remote-access settings.
- Investigate activity: Review authentication, SQL, firewall, and endpoint logs for unauthorized access, data exposure, or lateral movement; preserve relevant evidence.
- Restore safely: Recover from verified clean backups, then monitor closely for renewed access attempts or suspicious activity.
- Prevent recurrence: Add continuous monitoring and alerting for repeated login failures and unusual SQL activity, consistent with NIST CSF’s Protect, Detect, Respond, and Recover functions.
Stay Ahead in Cybersecurity
Explore career growth and education via Careers & Learning, or dive into Compliance essentials.
Explore engineering-led approaches to digital security at IEEE Cybersecurity.
Disclaimer: The information provided may not always be accurate or up to date. Please do your own research, as the cybersecurity landscape evolves rapidly. Intended for secondary references purposes only.
Cyberattacks-V1
