vendor binary

The Kingslayer EvLog Supply Chain Attack

Updated 5 Oct 2026 · Incident date 9 Apr 2015

A trojanized EvLog build from Altair Technologies and EventID.net opened a channel to outsiders and downloaded hidden software from 9 to 25 April 2015.

RSA named the operation Kingslayer. Krebs reports that the vendor posted a short notice in June 2016.

What happened

Attackers replaced a legitimate Windows event log tool with a backdoored build.

  • They compromised both the download page and the update server.
  • Existing installs downloaded the bad version at their next update check. New installs got it too.
  • RSA confirmed that at least one system administrator at a defense contractor was infected.
  • RSA took control of the command server domain oraclesoft[dot]net in April 2016.
  • SecurityWeek reports a link to Chinese APT groups known as Shell Crew and Codoso.

Krebs reports that the bad build shipped from 9 to 25 April 2015. The vendor, Altair Technologies of Mississauga, Ontario, did not tell customers directly.

Affected versions

  • The EvLog build downloaded from EventID.net or received through the updater from 9 to 25 April 2015.
  • The sources give no build number for the trojanized file.

Indicators of compromise

  • Command server domain: oraclesoft[dot]net. RSA sinkholed it in April 2016.
  • An EvLog install or update between 9 and 25 April 2015.
  • Outbound requests from an administrator workstation to the domain above.

How to check

Search archived DNS and proxy logs for the command domain. Replace the path with your own log folder.

zgrep -il "oraclesoft.net" /var/log/dns/* 2>/dev/null

What to do now

  1. Find every machine where EvLog ran, and the dates of install and update.
  2. If it ran between 9 and 25 April 2015, treat that machine as compromised and rebuild it.
  3. Reset the logins that the administrator used on that machine.
  4. Remove EvLog if you no longer use it.

Frequently asked questions

Who used the EventID.net portal?

Krebs reports users included five major defense contractors and four major telecom providers. Not all of them ran the bad build.

Did other products carry the bad build?

Krebs lists EventReader and Firegen from the same owner as possibly hit.

Sources

  1. krebsonsecurity.com/2017/02/how-to-bury-a-major-breach-notification/
  2. securityweek.com/serious-breach-linked-chinese-apts-comes-light/

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