What we know (technically) about EyePyramid
WARNING: this is the most up to date version among the various posts that I've released. So, please try to refer to this. Despite being the most up to date one, it's not guaranteed to be 100% accurate: I publish modifications and updates as I analyze the technical info at my disposal, trying to do my best to keep up.
This personal note, translation of its Italian version “Cosa sappiamo su EyePyramid,” is meant to be a container of distilled technical information currently available on the EyePyramid case. It is mainly based on the only official source, slightly enriched through some OSINT and personal searches.
Please feel free to comment here, or send me feedback at via email to: federico at maggi dot cc.
Sensitive information was exfiltrated from high-value targets on the Italian scene, for instance:
- 18327 usernames
- 1793 passwords
- keystrokes stolen via a keylogger
Roughly, 87GB of data overall, of course there is much more bejond this, but I don't want to repeat what's already clearly written in the PDF linked above.
Since 2012. Earlier versions of the malware malware (of uknonwn origin, except some speculations that would link this to Project Sauron, which I don't believe) have been probably used in 2008, 2010, 2011, and 2014 in various spear-phishing campaings (against various targets, including Italian targets).
Who are the victims?
The exfiltrated information is referred to, produced/exchanged by, or otherwise possessed by private and public Italian citizens, operating in key positions of the Italian State. The known domains of the victims are:
- enav.it (unconfirmed)
From what we know, the attacker (or the attackers):
- cooked (or, better, modified an existing) malware that, among the traditional C2 communication techniques, it leverages MailBee.NET.dll APIs (a .NET library used for building mail software) to send the exfiltrated data out to dropzones. In particular, one of the MailBee license keys used by the malware writer is (? = uknownw) MN600-D8102?501003102110C5114F1?18-0E8CI (other keys are reported below) 2. comprmised (we don't know how) some email accounts (at least 15, from what we know). In particular, accounts belonging to various attorneys and associates, 3. the attacker (or the malware, it's not really clear) connects via Tor (for what is worth, the only known exit node is 37.49.226[.]236)
- using an email mail server (among the known ones, Aruba's MX 62.149.158[.]90) the attacker sends spear-phisihing email messages to the victims using the compromised accounts s the sender, containing a malicious attachment (unverified information: someone believes the attachment is a PDF)
- wait for the victims to open the attachment, which drops the malware executable 6. the malware sends exfiltrated data to various dropzones (i.e., email addresses in use by the attacker)
Related Samples (not yet 100% EyePyramid!)
This has been found via “MSIL/Cribz.a”, a clue by @ReaQta together with @emgent who convinced me that it's actually a relevant sample. I'm still skeptical, though. It's definitely relevant and related based on what's in it, but it's not 2016's EyePyramid.
An analysis has been started on Hybrid Analysis (not by me).
Encryption (from the related sample)
I found these mailservers being used by the malware. Not clear (yet) if its only for sending emails, or for information harvesting too.
Incomplete list of targeted files
used by the recent variant as dropzones:
- ulpi715@gmx[.]com - not sure about this
used in 2010 for the same purpose
used as senders in spear-phishing messages
other (cannot link it to anything)
Hosts/domains (some are C&C)
- URL paths (likely related to traffic directed to the C2)
- 217.115.113[.]181 (Ireland)
- 216.176.180[.]188 (Seattle, Washington, US)
- 65.98.88[.]29 (Clifton, New York, US)
- 199.15.251[.]75 (Baltimore, Maryland, US)
- 216.176.180[.]181 (Seattle, Washington, US)
- qbpye.exe - this is the name of an executable written by the malware (obtained from related sample analysis)
- there are at least other names used by the malware to plant itself on the FS, but these are not confirmed IOCs, so I'm not going to share them yet
- InfoPyramid.accdb - database found on hostpenda[.]com containing exfiltrated data
Building info (and other source-code-related info)
From the related sample above, I could determie that the code is written in .NET (>= 4.5.x), source-code-level obfuscation, plus some other obfuscation on the executable. Uses reflection, and I can confirm the use of MailBee, although I haven't been able to recover the license key.
- Visual Studio was used to build “Eye Manager,” (allegedly the name of the botmaster component)
- Hangeron (module name)
- Mailfaker (module name)
- fHangeron.Menu.Web.vb (file name)
- m.Core.vb (file name)
- cEmailJob.vb (file name)
- mWakeUP.vb (file name)
- ds1 (variable name)
- ms1 (variable name)
- dc1 (variable name)
- ds2 (variable name)
- ms2 (variable name)
- dc2 (variable name)
- MailDemon (odd: any English-speaking dev would have used “MailDaemon”, unless this is a typo introduced in the Police report)
- MN600-849590C695DFD9BF69481597241E-668C (.NET MailBee license key)
- MN600-841597241E8D9BF6949590C695DF-774D (.NET MailBee license key)
- MN600-3E3A3C593AD5BAF50F55A4ED60F0-385D (.NET MailBee license key)
- MN600-AD58AF50F55A60E043E3A3C593ED-874A (.NET MailBee license key)
- PCMDPWD (tiro a indovinare: PC Mail Daemon Password?)