Skip to main content
Mallory
MalwareUsed by 1 actor

Briba

Briba is a malware family observed in targeted APT activity and associated in the provided content with the Sunshop Campaign and broader Sunshop Digital Quartermaster-linked operations. FireEye collected one Briba sample among 110 malware binaries tied to 11 linked APT campaigns, where the overall malware set was primarily detected as Trojan.APT.9002, PoisonIvy, Gh0st, Kaba, and Briba. In the Sunshop Campaign, a Briba sample with MD5 6fe0f6e68cd9cc6ed7e100e7b3626665 was found connecting to the command-and-control infrastructure at IP address 58.64.205.53 via nameserver1.zapto.org. The same campaign used strategic web compromises and exploit delivery, including CVE-2013-1347, CVE-2013-2423, and CVE-2013-1493, to deploy malware families including 9002 RAT, Poison Ivy, and Briba. The content also states that the Sunshop Group had used Briba in past campaigns, including a related attack exploiting a Flash zero-day. On infected Windows hosts, Briba uses rundll32 within Registry Run Keys or Startup Folder entries to execute malicious DLLs, indicating a persistence and execution mechanism based on malicious DLL loading. The content further states that Briba downloads files onto infected hosts. FireEye detects Briba as Backdoor.APT.IndexASP. High-confidence indicators directly mentioned in the content include MD5 6fe0f6e68cd9cc6ed7e100e7b3626665, C2 domain nameserver1.zapto.org, and associated IP address 58.64.205.53.

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

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

View more details
APT19

After further research into 58.64.205.53 with our friends at Mandiant we uncovered a Briba sample with the MD5 6fe0f6e68cd9cc6ed7e100e7b3626665 that connected to this IP address.

via fireeyefireeye.com
MITRE ATT&CK

Techniques & procedures

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

Persistence

3 techniques
T1112Modify RegistryEvidence1

Across the content, malware repeatedly 'adds Registry Run keys', 'creates Registry entries', 'modifies the Windows Registry', or 'overwrites registry keys' to maintain persistence.

T1543.003Windows ServiceEvidence2

“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”

T1547.001Registry Run Keys / Startup FolderEvidence4

The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, or .lnk files in the Startup folder.

T1543.003Windows ServiceEvidence2

“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”

T1547.001Registry Run Keys / Startup FolderEvidence4

The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, or .lnk files in the Startup folder.

Stealth

1 technique
T1218.011Rundll32Evidence1
TacticStealth
T1112Modify RegistryEvidence1

Across the content, malware repeatedly 'adds Registry Run keys', 'creates Registry entries', 'modifies the Windows Registry', or 'overwrites registry keys' to maintain persistence.

T1105Ingress Tool TransferEvidence1
INDICATORS OF COMPROMISE

IOCs tracked for this family

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

View more in app
Network
2 tracked

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

Hashes
1 tracked

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

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app13 years ago
hash.md5●●●●●●●●●●●●View more in app13 years ago
ip.v4●●●●●●●●●●●●View more in app13 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 matching3

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

Threat actor attribution1

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 mapping5

Every documented technique, ranked by evidence weight.

Researcher chatter

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