Huntress Reconstructs INC Ransomware Attack Using Surviving Evidence

· Original article ↗

Summary

Huntress reconstructed parts of an INC ransomware attack from post-incident evidence, finding scheduled-task persistence, RDP lateral movement, AnyDesk deployment, and a BYOVD tool used to disable security controls. The initial access vector remains unknown.

Key points

  • The ransomware affected at least 175 endpoints, with traces of attacker activity found on domain controllers.
  • Investigators could not determine the initial access vector because the incident response began after the attack and some telemetry had expired.
  • Early-August activity included obfuscated PowerShell persistence through a scheduled task and lateral movement over RDP using a compromised account.
  • After a 17-day lull, AnyDesk was used to deploy tools, including a vulnerable driver used to disable security controls.
  • Attackers used Impacket's atexec.py to run tools through temporary scheduled tasks and launch INC ransomware.
  • A second ransom note threatened a public announcement and contact with the victim's stakeholders, and listed allegedly stolen files.
  • Huntress recommends monitoring unusual scheduled tasks, remote-management tools, and driver services, alongside MFA, least privilege, offline backups, and rapid isolation plans.

Article Details

Attack Vectors
  • The initial access vector could not be determined.
  • A compromised user account was used for lateral movement between endpoints via Remote Desktop Protocol.
  • AnyDesk was installed and used to deploy netscan.exe and a vulnerable-driver tool to multiple endpoints.
  • Impacket's atexec.py was used to execute tools remotely by creating and running temporary scheduled tasks.
  • A PowerShell implant referenced by a scheduled task communicated with throughoutes[.]net.
Defensive Notes
  • Limit and monitor remote access, enforce multi-factor authentication, and restrict privileged accounts to the systems they need.
  • Monitor for unusual scheduled tasks, unexpected remote-management tools, new or unsigned driver services, and activity designed to disable security products.
  • Maintain tested offline backups and an incident response plan that includes rapid isolation procedures.
  • Preserve and review available artifacts, including scheduled tasks, remote-access tooling, driver services, event logs, and ransom notes.

Indicators of compromise

TypeIndicatorContext
DOMAINthroughoutes[.]netDomain contacted by the obfuscated PowerShell implant.
IPV4213[.]111[.]185[.]108Command-and-control IP associated with the observed AnyDesk installation.

MITRE ATT&CK

People

Malware

Vendors

Products

Tools

Related Articles