This post was syndicated from: SANS Internet Storm Center, InfoCON: green and was written by: SANS Internet Storm Center, InfoCON: green. Original post: at SANS Internet Storm Center, InfoCON: green
This is a guest diary submitted by Brad Duncan.
In September 2014 after the Neutrino exploit kit (EK) had disappeared for 6 months, it reappeared in a different form. It was first identified as Job314 or Alter EK before Kafeine revealed in November 2014 this traffic was a reboot of Neutrino .
This Storm Center diary examines Neutrino EK traffic patterns since it first appeared in the Spring of 2013.
Neutrino EK: 2013 through early 2014
Neutrino was first reported in March 2013 by Kafeine on his Malware Dont need Coffee blog . It was also reported by other sources, like Trend Micro .
Heres a sample of Neutrino EK from April 2013 using HTTP over port 80:
Shown above: Neutrino EK traffic from April 2013.
By the summer of 2013, we saw Neutrino use HTTP over port 8000, and the traffic patterns had evolved. Heres an example from June 2013, back when I first started blogging about malware traffic :
Shown above: Neutrino EK traffic from June 18th, 2013.
In October 2013, Operation Windigo (an on-going operation that has compromised thousands of servers since 2011) switched from using the Blackhole EK to Neutrino .
Before Neutrino EK disappeared in March of 2014, I usually found it in traffic associated with Operation Windigo. Here are two examples from February and March 2014  :
Shown above: Neutrino EK traffic from February 2nd, 2014.
Shown above: Neutrino EK traffic from March 8th, 2014.
March 2014 saw some reports about the EKs author selling Neutrino . Later that month, Neutrino disappeared. We stopped seeing any sort of traffic or alerts on this EK.
Neutrino EK since December 2014
After Kafeine made his announcement and EmergingThreats released new signatures for this EK, I was able to infect a few VMs. Heres an example from November 2014 :
Shown above: Neutrino EK traffic from November 29th, 2014.
Traffic patterns have remained relatively consistent since Neutrino reappeared. I infected a VM on February 2nd, 2015 using this EK. Below are the HTTP requests and responses to Neutrino EK on vupwmy.dout2.eu:12998.
- GET /hall/79249/card/81326/aspect/sport/clear/16750/mercy/flash/clutch/1760/
- HTTP/1.1 200 OK (text/html) – Landing page
- GET /choice/34831/mighty/drift/hopeful/19742/fantastic/petunia/fine/12676/
- HTTP/1.1 200 OK (application/x-shockwave-flash) – Flash exploit
- GET /nowhere/44312/clad/29915/bewilder/career/pass/sinister/
- HTTP/1.1 200 OK (text/html) – No actual text, about 25 to 30 bytes of data, shows up as Malformed Packet in Wireshark.
- GET /marble/1931/batter/21963/dear/735/yesterday/6936/familiar/37370/
- HTTP/1.1 200 OK (application/octet-stream) – Encrypted malware payload
- GET /lord.phtml?horror=64439push=75359pursuit=washfond=monsieur
- HTTP/1.1 404 Not Found OK (text/html)
- GET /america/86960/seven/quiet/blur/belong/traveller/12743/gigantic/96057/
- HTTP/1.1 404 Not Found OK (text/html)
The malware payload sent by the EK is encrypted.
Shown above: Neutrino EK sends the malware payload.
I extracted the malware payload from the infected VM. If youre registered with Malwr.com, you can get a copy from:
This malware is similar to previous Vawtrak samples Ive seen from Neutrino and Nuclear EK last month  .
Exploit kits tend to evolve over time. You might not realize how much the EK has changed until you look back through the traffic. Neutrino EK is no exception. It evolved since it first appeared in 2013, and it significantly changed after reappearing in December 2014. It will continue to evolve, and many of us will continue to track those changes.
Brad Duncan is a Security Researcher at Rackspace, and he runs a blog on malware traffic analysis at http://www.malware-traffic-analysis.net
(c) SANS Internet Storm Center. https://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.