Huntress Details SQL Injection Attack and Attacker’s Post-Compromise Activity

· Original article ↗

Summary

Huntress describes an attacker entering a Windows server through SQL injection, then enabling Remote Desktop, creating an admin account, disabling Defender, and installing BadIIS and XMRig. It urges fixing the entry point as well as removing payloads.

Key points

  • Huntress traced the attacker’s access to a web page that failed to validate input, enabling SQL injection against a Windows server.
  • The attacker enumerated running services and sent the results to a server they controlled.
  • They enabled Remote Desktop, created and used a local administrator account, and disabled Windows Defender; other security monitoring tools remained active.
  • The attacker installed BadIIS modules on the IIS web server, which can be used to manipulate website traffic.
  • They deployed XMRig as a Windows service for persistence, hid its files, and installed an additional detection-evasion tool.
  • The attacker downloaded PowerShell scripts and batch files and ran PowerShell silently with execution-policy restrictions bypassed.
  • Huntress recommends addressing the original SQL injection flaw as well as removing attacker tools, and also advises reducing exposed services, using MFA, and maintaining patching and monitoring.

Article Details

Attack Vectors
  • An unvalidated web-page input enabled SQL injection, which the attacker used to access the underlying Windows machine.
  • After gaining access, the attacker listed running services and sent the results to a server they controlled.
  • The attacker enabled Remote Desktop, created a local account, added it to the local Administrators group, and used it to log in.
  • The attacker disabled Windows Defender and installed BadIIS modules on the IIS web server.
  • The attacker installed XMRig for cryptocurrency mining, configured it to run as a Windows service, and used file attributes to hide its files.
  • The attacker downloaded PowerShell scripts and batch files from external servers and ran PowerShell silently, bypassing script execution policies.
Defensive Notes
  • Fix the original SQL injection flaw as part of incident response; removing malware and accounts without closing the entry point may allow re-entry.
  • Maintain an inventory of systems, applications, and versions; reduce exposed services, and remove unnecessary or unauthorized items.
  • Restrict access to authorized users and use multi-factor authentication wherever possible.
  • Patch active applications regularly and include them in monitoring coverage.
  • Investigate the root cause of incidents rather than stopping after removing obvious malware.

MITRE ATT&CK

Malware

Vendors

Products

Related Articles