vendor binary

The NetSarang Xshell ShadowPad Supply Chain Attack

Updated 5 Oct 2026 · Incident date 18 Jul 2017

Xshell 5 Build 1322 and other NetSarang builds shipped the ShadowPad backdoor inside nssock2.dll on 18 July 2017.

The library carried NetSarang's own certificate. Kaspersky found it and told NetSarang privately on 4 August 2017.

What happened

A malicious library was built into five server management tools and signed by the vendor.

  • nssock2.dll was compiled on 13 July 2017.
  • The software went live on 18 July.
  • The first layer sent the computer name, domain and user name to a command server every eight hours.
  • The attacker turned it on with a specially built DNS TXT record.
  • It can then download and run any code.

NetSarang pulled the builds after the report, so the exposure ran at least 17 days. Kaspersky confirmed a financial firm in Hong Kong as a victim.

Affected versions

  • Xshell 5 Build 1322.
  • Xmanager Enterprise 5 Build 1232.
  • Xmanager 5 Build 1045.
  • Xftp 5 Build 1218.
  • Xlpd 5 Build 1220.
  • Kits from April 2017 or earlier are not affected. Tenable names Xshell 5 Build 1326 as the fix.

Indicators of compromise

  • File: nssock2.dll, MD5 97363d50a279492fda14cbab53429e75, signed by NetSarang.
  • MD5 of Xshell 5 Build 1322: b2c302537ce8fbbcff0d45968cc0a826.
  • MD5 of Xmanager Enterprise 5 Build 1232: 0009f4b9972660eeb23ff3a9dccd8d86.
  • MD5 of Xmanager 5 Build 1045: b69ab19614ef15aa75baf26c869c9cdd.
  • MD5 of Xftp 5 Build 1218: 78321ad1deefce193c8172ec982ddad1.
  • MD5 of Xlpd 5 Build 1220: 28228f337fdbe3ab34316a7132123c49.
  • Domains: ribotqtonut[.]com, nylalobghyhirgh[.]com, jkvmdmjyfcvkf[.]com, bafyvoruzgjitwr[.]com, xmponmzmxkxkh[.]com, tczafklirkl[.]com, notped[.]com, dnsgogle[.]com, operatingbox[.]com, paniesx[.]com, techniciantext[.]com.
  • Kaspersky detection name: Backdoor.Win32.ShadowPad.a.

How to check

Hash the library in each NetSarang install folder. A match with 97363d50a279492fda14cbab53429e75 means the backdoored library is present.

Get-ChildItem "C:\Program Files*\NetSarang" -Recurse -Filter nssock2.dll | Get-FileHash -Algorithm MD5

Search DNS logs for the domains above.

What to do now

  1. Update every NetSarang product. Xshell 5 Build 1326 or later is the fix.
  2. If you ran a bad build, check DNS logs for the domains above and hunt on those hosts.
  3. Rotate the passwords and keys used from those machines.
  4. Block the domains.

Frequently asked questions

Which NetSarang builds contained ShadowPad?

Xshell 5 Build 1322, Xmanager Enterprise 5 Build 1232, Xmanager 5 Build 1045, Xftp 5 Build 1218 and Xlpd 5 Build 1220.

How did ShadowPad activate?

The attacker sent a specially built DNS TXT record. Until then it sent only basic host data every eight hours.

Sources

  1. securelist.com/shadowpad-in-corporate-networks/81432/
  2. thehackernews.com/2017/08/netsarang-server-management.html
  3. tenable.com/plugins/nessus/102713

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library