@obilodeau
and special thanks to Thomas Dupuy (@nyx__o)
An update on this atypical embedded Linux botnet
Statically linked stripped ELF challenges
Moose DNA (description)
Moose Herding (the Operation)
A Strange Animal
Latest Developments
Malware Researcher at ESET
Infosec lecturer at ETS University in Montreal
Previously
infosec developer, network admin, linux system admin
Co-founder Montrehack (hands-on security workshops)
Founder NorthSec Hacker Jeopardy
No imports (library calls) present
All the code bundled together down to kernel syscall
Disassembler (if available for arch) doesn’t help much
GCC and GNU libc is always changing so compiled binaries always change
Little IDA FLIRT signatures available (if any)
µClibc, eglibc, glibc, musl, …
Map syscalls with IDA script
But libc is too big it is still too much
Reproduce environment (arch, libc/compiler versions)
Build libraries w/ symbols under same conditions
Use bindiff to map library functions
Focus on malware code
aka Malware description
Named after the string "elan" present in the malware executable
The Slovak rock band (from 1969 and still active)
Pivot through firewalls
Home-made NAT traversal
Custom-made Proxy service
only available to a set of whitelisted IP addresses
Remotely configured generic network sniffer
DNS Hijacking
Tries to replicate via aggressive scanning
Will dedicate more resources to scan near current external IP
Will also scan on LAN interfaces
Will not reinfect an infected device
Can replicate across architectures
C&C is made aware of new compromises
Statically linked binary stripped of its debugging symbols
Hard to reproduce environment required for malware to operate
Misleading strings (getcool.com)
The Malware Operation
Network sniffer was used to steal HTTP Cookies
Twitter: twll
, twid
Facebook: c_user
Instagram: ds_user_id
Google: SAPISID
, APISID
Google Play / Android: LAY_ACTIVE_ACCOUNT
Youtube: LOGIN_INFO
Nature of traffic
Protocol
Targeted social networks
Whitelist means we can’t use the proxy service to evaluate malware population
Blind because of HTTPS enforced on social networks
DNS Hijacking’s Rogue DNS servers never revealed
not in the DDoS or bitcoin mining business
no x86 variant found
controlled by a single group of actors
No persistence mechanism
No shell access for operators
In social network fraud, network sniffer irrelevant
DNS Hijacking possible but only for few devices
No ad fraud, spam, DDoS, etc.
Few weeks after the publication the C&C servers went dark
After a reboot, all affected devices should be cleaned
But victims compromised via weak credentials, so they can always reinfect
On the lookout for Moose v2
Looked at over 150 new samples targeting embedded Linux platforms
Linux/Aidra, Linux/Dofloo (AES.DDoS), Linux/DNSAmp (Mr.Black), Linux.Gafgyt and Linux/Tsunami
Still no Moose update…
New sample this Saturday
New proxy service port (20012)
New C&C selection algorithm
Lots of differences
Still under scrutiny
Embedded malware
Not yet complex
Tools and processes need to catch up
a low hanging fruit
Prevention simple
Thank you!
@obilodeau
and special thanks to Thomas Dupuy (@nyx__o)