Skip to main content
Mallory
MalwareUsed by 2 actors

ISMAgent

ISMAgent is an OilRig-associated malware family used for command-and-control over DNS, with HTTP as another C2 channel and DNS tunneling used as a fallback when HTTP is unavailable. According to the provided content, ISMAgent issues DNS AAAA requests using the DnsQuery_A API and communicates with actor-controlled domains via specially crafted subdomains. It generates a unique session identifier with CoCreateGuid and uses a hyphen-stripped GUID in its beacon structure. The malware base64-encodes system data with character substitutions and transmits it in 13-character chunks within DNS subdomains, then signals completion with an "n.<count>.f" query. It uses hardcoded IPv6 acknowledgement values, including a67d:0db8:a2a1:7334:7654:4325:0370:2aa3 to indicate operational readiness and a67d:0db8:85a3:4325:7654:8a2a:0370:7334 to continue sending data. ISMAgent determines the number of download queries to issue by parsing the last two hexadectets of a C2-provided IPv6 address beginning with a67d:0db8:85a3:4325:7654. The content states that ISMAgent can receive commands embedded in IPv6 answers, including examples that execute PowerShell to write to C:\Users\Public\file.txt and later upload that file’s contents through the DNS tunnel. The malware is part of OilRig’s broader malware arsenal, and the provided material associates OilRig with spear-phishing, supply chain attacks, and DNS-tunneling tradecraft.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

2 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
Greenbug

ISMAgent uses the DnsQuery_A API function to issue DNS AAAA requests to resolve custom crafted subdomains at an actor owned domain to send data to and receive commands from OilRig.

via palo alto networks unit 42 blogunit42.paloaltonetworks.com
OilRig

ISMAgent uses the DnsQuery_A API function to issue DNS AAAA requests to resolve custom crafted subdomains at an actor owned domain to send data to and receive commands from OilRig.

via palo alto networks unit 42 blogunit42.paloaltonetworks.com
MITRE ATT&CK

Techniques & procedures

6 distinct techniques documented for this family, organized by ATT&CK tactic.

Execution

1 technique
T1059.001PowerShellEvidence1
TacticExecution

"The Helminth Trojan came in two forms, a portable executable version and a PowerShell version"; "...ISMAgent... would run a PowerShell script..."; "QUADAGENT... obtain a PowerShell script that it will replace itself with"; "BONDUPDATER... download a new PowerShell... script"

Stealth

1 technique
T1027Obfuscated Files or InformationEvidence1
TacticStealth

"The two encoding methods used by these tools... base16 and base64"; "...custom base64 encoder to strip out non-alphanumeric characters"; "...encoding mechanism... splits each hexadecimal byte into two nibbles..."

Discovery

2 techniques
T1033System Owner/User DiscoveryEvidence1
TacticDiscovery

"The Trojan will first create a unique system identifier by executing the 'whoami' command"; "...base64 encoded computername\username"

T1082System Information DiscoveryEvidence1
TacticDiscovery

"ALMA... gathering the user name and windows product key"; "...dot variant also gathers the computer name and the serial number of '\\.\PhysicalDrive'"; "...send system specific data... <domain>\<username>:pass"

T1071.004DNSEvidence1

"Depending on the tool, A, AAAA, and TXT query types have been used by OilRig for tunneling" and "...use DNS queries to resolve specially crafted subdomains... and the answers... to receive data from the C2." | "...malware can use DNS queries and answers to act as a command and control channel... tools that rely on DNS tunneling used by an adversary known as OilRig."

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence1

"...upload the results to the C2 via the DNS tunnel"; "...exfiltrate the contents of each file in this folder"; "...upload its contents to the C2 server"; "...transmitting data to the C2 in the queried subdomains"

INDICATORS OF COMPROMISE

IOCs tracked for this family

5 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
3 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
2 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app7 years ago
hash.sha256●●●●●●●●●●●●View more in app7 years ago
ip.v6●●●●●●●●●●●●View more in app7 years ago
hash.sha256●●●●●●●●●●●●View more in app7 years ago
ip.v6●●●●●●●●●●●●View more in app7 years ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching5

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution2

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping6

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.