1-minute read of a 5 min report

Sliver Toolkit Scripts Credential Theft and Persistent Domain Access

By

1-minute read

What a defender needs to know

A recovered Windows post-exploitation kit shows preparations to control an unnamed US organization’s Active Directory estate. The scripts created a non-expiring Domain Admin account, disabled eight endpoint-security services, collected credentials through LSASS, Mimikatz, and registry-hive copies, and prepared deployment across 18 internal hosts.

The victim-specific mechanism paired a planted Active Directory DNS record with a whitelist change in the organization’s DNS filter. That let publisherresolution[.]com resolve internally and pass the control meant to block it. The same domain was the first command server recorded in Ethereum contract 0xb3f2897f2bc797e5b9033faef8c81e92b01cb831, tying the Sliver strand to a Node.js implant that rotated through five domains.

The scripts show prepared capabilities and victim knowledge. Execution records would be needed to determine which commands ran. The corpus contained no encryptor, wiper, or recovery-inhibition artifact, although Huntress linked the infrastructure to a confirmed ransomware incident.

Hunt for an account created outside normal provisioning and added directly to Domain Admins, a hidden SYSTEM task that re-fetches task_39.ps1, a 60-second beacon with no measured jitter, and the malformed User-Agent Chrome/108.0.6602.492. The Sliver address was 193[.]233[.]202[.]17; itemrange[.]com was the latest contract-resolved domain.

Reset domain credentials, restore the DNS-filter whitelist, rotate its administrator credential, remove planted internal DNS records, and restore RDP Network Level Authentication. Verify that the unauthorized account and weekly task are absent and that endpoint, DNS, and network telemetry show no campaign markers.

Primary sources