Shown above: Its always fun to find ransomawre thats not Cerber or Locky. Sage is yet another family of ransomware inSage 2.0 Ransomware, (Sat, Jan 21st)_HackDig : Dig high-quality web security articles for hackerHackDig" />

HackDig : Dig high-quality web security articles for hacker

«No Previous
No Next

Sage 2.0 Ransomware, (Sat, Jan 21st)

2017-01-21 16:30


On Friday 2017-01-20, I checked a malicious spam (malspam) campaign that normally distributes Cerber ransomware. That Friday it delivered ransomware Id never seen before called Sage. More specifically, it was Sage 2.0." />
Shown above: Its always fun to find ransomawre thats not Cerber or Locky.

Sage is yet another family of ransomware in an already crowded field. It was noted on BleepingComputer forums back in December 2016 [1, 2], and Sage is a variant of CryLocker [3]. Unfortunately, I cant find an in-depth write-up on Sage that I like. With that in mind, this diary examines Sage 2.0.

The malspam

Emails from this particular campaign generally have no subject lines, and they always have no message text. The only content is a zip attachment containing a Word document with a malicious macro that downloads and installs ransomware. Sometimes, I" />
Shown above: Data from a spreadsheet tracking the malspam (1 of 3).

Often, the recipients name is part of the attachments file name. I replace those names with [recipient] before I share any info. A more interesting fact is the attachments are often double-zipped." />
Shown above:" />
Shown above:" />
Shown above: Another example of the Word document with a malicious macro.

The Word document macros or .js files are designed to download and install ransomware." />
Shown above: Data from a spreadsheet tracking the malspam (3 of 3), mostly Sage 2.0.

The infected host

Under default settings, an infected Windows 7 host will present a UAC window before Sage continues any further." />
Shown above: UAC pop-up caused by Sage.

The infected Windows host has an image of the decryption instructions as the desktop background. Theres also an HTML file with the same instructions dropped to the desktop. The same HTML file is also dropped to any directory with encrypted files. .sage" />
Shown above: Desktop of an infected Windows host.

Sage ransomware is kept persistent by a scheduled task, and its stored as an executable in the user" />
Shown above: Sage ransomware and its scheduled task for persistence.

Following the decryption instructions should take you to a Tor-based domain with a decryptor screen." />
Shown above: The Sage 2.0 decryptor.

Sage 2.0 traffic

Sage ransomware generates post-infection traffic. In the image below, an initial HTTP GET request to was caused by a .js file retrieving the ransomware." />
Shown above:" />
Shown above: TCP stream of an HTTP request for the post-infection traffic.

When the callback domains for Sage didnt resolve in DNS, the infected host sent UDP packets sent to over 7,000 IP addresses. I think this could be UDP-based peer-to-peer (P2P) traffic, and it appears to be somehow encoded or encrypted. BleepingComputers September 2016 write-up on CryLocker shows the same type of UDP post-infection traffic, but CryLocker" />
Shown above:" />
Shown above:" />
Shown above: Examining one of the UDP packets.

Indicators of Compromise (IOCs)

Below are IOCs for Sage 2.0 from Friday 2017-01-20:

Ransomware downloads caused by Word document macros or .js files:

  • port 80 - - GET /read.php?f=0.dat
  • port 80 - - GET /read.php?f=0.dat
  • port 80 - - GET /user.php?f=0.dat

Post-infection traffic:

  • port 80 - - POST /
  • port 80 - - POST /
  • (DNS queries did not resolve)
  • Various IP addresses, UDP port 13655 - possible P2P traffic

Tor-based domains to view the decryption instructions:

  • 7gie6ffnkrjykggd.onion

SHA256 hashes for the Sage 2.0 ransomware samples:

  • 0ecf3617c1d3313fdb41729c95215c4d2575b4b11666c1e9341f149d02405c05 (352,328 bytes)
  • 362baeb80b854c201c4e7a1cfd3332fd58201e845f6aebe7def05ff0e00bf339 (352,328 bytes)
  • 3b4e0460d4a5d876e7e64bb706f7fdbbc6934e2dea7fa06e34ce01de8b78934c (352,328 bytes)
  • 8a0a191d055b4b4dd15c66bfb9df223b384abb75d4bb438594231788fb556bc2 (352,328 bytes)
  • ccd6a495dfb2c5e26cd65e34c9569615428801e01fd89ead8d5ce1e70c680850 (352,328 bytes)

Examples of locations on the infected Windows host where Sage 2.0 was made persistent:

  • C:Users[username]AppDataRoaminggNwO5YoE.exe
  • C:Users[username]AppDataRoamingwiqpNWm7.exe
  • NOTE: File names appear to consists 8 random alphabetic characters with an .exe suffix.

Final words

An important note: URLs for the ransomware download will send Cerber one day, but the same URLs can send something like Sage ransomware the next.

Im not sure how widely-distributed Sage ransomware is. Ive only seen it from this one malspam campaign, and Ive only seen it one day so far. Im also not sure how effective this particular campaign is. It seems these emails can easily be blocked, so few end users may have actually seen Sage 2.0.

Still, Sage is another name in the wide variety of existing ransomware families. This illustrates how profitable ransomware remains for cyber criminals.

Pcaps, emails, malware, and artifacts for this diary are available here.

Brad Duncan
brad [at]



(c) SANS Internet Storm Center. Creative Commons Attribution-Noncommercial 3.0 United States License.

Source: ssr;pma&95912=diyrots?lmth.yraid/ude.snas.csi

Read:6084 | Comments:0 | Tags:No Tag

“Sage 2.0 Ransomware, (Sat, Jan 21st)”0 Comments

Submit A Comment



Blog :

Verification Code: