Jump to content

Project Sauron

From Wikipedia, the free encyclopedia

Project Sauron, also named ProjectSauron and Remsec[1] is a computer malware discovered in 2016,[2][3][4] targeting only Windows systems.[5] It has been spying on computers at governments and organizations for five years.[6] It can steal encryption keys, collect information from air-gapped computers, and record keystrokes without being detected.[7] It was discovered by security experts from Symantec (now part of Broadcom) and Kaspersky Lab,[1] which was reportedly found on various targets in China, Russia, Iran, Sweden, Belgium, and Rwanda.[8] Due to its complex and well-designed structure, the malware is believed to have been developed by a state-backed hacking group or an intelligence agency. Although the malware is considered to have been widely eradicated following its public disclosure, Project Sauron might still remain active on systems that are not protected by Kaspersky Lab solutions.[9] The initial infected medium that led to the spread of Project Sauron still remains unknown.[10]

Overview

[edit]

What made ProjectSauron stand out from other malware at the time of its discovery was its unique design tailored specifically for almost all of its targets,[11][12] along with its ability to remain "invisible" to all known and installed malware detection systems on the infected systems. Following the discovery of the malware, infected systems in Russia, Iran, and Rwanda were found across government agencies, scientific research centers, military computer systems, telecommunications providers, and financial institutions.[13] Besides collecting plain text and keystroke data from infected systems, ProjectSauron also primarily targeted encryption software used for secure communications, leading to the hypothesis that the malware was designed to gather valuable intelligence.[14]

In September 2015, Kaspersky's Anti-Targeted Attack Platform detected unusual network traffic in a client organization's network, which led to the discovery of a malicious program registered as a password filter service residing in the memory of the domain controller servers.[15] This program also had access to administrators' passwords in clear text and included a backdoor that was activated to capture login credentials or changed passwords in plain text every time local or remote users typed them in.[16] The malware was also discovered to steal encryption keys, configuration files, and IP addresses, as well as performing real-time user status updates. It exfiltrated data stealthily, while incorporating strong encryption algorithms such as RC6, RC5, RC4, AES, and Salsa20.[17] Forensic analysts stated that the malware had been active since June 2011 and remained so until its discovery in April 2016.[17] As part of the malware itself, a Lua script[18] running on a modified Lua interpreter is used to execute the malware’s internal scripts and modules.[19] The use of Lua in malware is highly uncommon, with only two known cases prior to this: the Flame and Animal Farm attacks.[18] Since the Lua script included the term "Sauron", the malware was codenamed "ProjectSauron" or "Project Sauron" by Kaspersky.[14] HEUR:Trojan.Multi.Remsec.gen, a variant of ProjectSauron is also detected by Kaspersky Lab.[20] The term "Remsec" of the variant led to the codenamed "Remsec", which is used as an alternative name for the malware.

Technical

[edit]

In several cases, forensic analysts discovered that ProjectSauron's droppers, residing on compromised administrator systems and registering as a password filter service, were distributed alongside legitimate software updates within the network. The dropper then downloaded additional payload of the malware from its designated external IP address.[21] Once fully downloaded, ProjectSauron started working as a backdoor.[11] If the system that the dropper is on doesn't have Internet access, that dropper can communicate with the others one on the local network that are connected to the Internet in order to download the full malware payload. All fully functional malware on infected systems within the network eventually begins silent data collection and exfiltration, blending their activities into the legitimate network traffic of the entire system.[16] If not all systems in the network have Internet access, those that do will act as intermediary servers, helping the others send collected data to the malware’s command-and-control (C&C) server.[16]

Infections of ProjectSauron also came from storage media, in which it disguised itself under filenames of legitimate software.[21] This approach was extremely efficient for systems that lack Internet access entirely. In that case, the malware reformatted the infected USB drive, adding a new partition of several hundred megabytes at the end of the device’s memory layout for its own purposes. This newly created partition is an encrypted virtual file system (VFS), which makes it unrecognizable by Windows.[22] By that method, an in-system permitted USB drive is free to carry out malicious actions on the system as long as it remains plugged in. With the collected data, whenever the infected USB is plugged into an Internet-connected system, it will begin transmitting the data to the C&C server. This process enables the transfer of data from air-gapped networks—i.e., those without Internet access—to Internet-connected systems, allowing the data to eventually reach the C&C server.[22] Forensic analysts stated that the encrypted VFS partition created by the malware doesn't facilitate data collection within the air gapped system, leading to the hypothesis that zero-day exploits might have been involved in the main partition of the USB drive. However, following the malware's public disclosure, no zero-day exploits associated with it have been found.[23]

The malware stole document with common file extensions, such as *.txt, *.doc, *.docx, *.ppt, *.pptx, *.xls, *.xlsx, and *.pdf; it also exfiltrated login credentials and user configuration files matching patterns like .*account, *login, *user, *name, .*pass, *email, mailaddress, *.conf, *.cfg, and others. The exfiltrated encryption keys were found to have file extensions including *.ppk, *.rsa, and *.key.[24]

For communication protocols, forensic analysts discovered that the malware used a wide range of well-known protocols, including HTTP, DNS, SMTP, TCP, UDP, and ICMP. The malware uses DNS for both real-time system reporting and data exfiltration.[25] The communication between the malware and its C&C server is carried out using its own protocol,[26] but forensic analysis has not determined its protocol suite, whether it operates at the transport layer or the application layer.

Aftermath

[edit]

Upon its public disclosure, ProjectSauron was reported to have been ceased by Kaspersky Lab. However, the damaged caused by the malware has neither been reported nor estimated. Kaspersky Lab initially reported infection cases in Russia, Iran, and Rwanda, while Symantec identified cases in other countries, including China, Sweden, and Belgium.[8] Forensic analysts even discovered file extensions in Italian among the malware’s targets, suggesting that Italian-speaking countries might also have been targeted, although no infections have been reported in those countries.[24]

There is no conclusive evidence identifying who was behind ProjectSauron,[27] but it can be inferred that it was a nation-state-sponsored operation due to its complexity and well-defined structure.[28] Although forensic analysis uncovered 28 domains linked to 11 IP addresses based in the United States and several European countries,[12] there is still no definitive evidence to conclude that those countries were behind the attack. This could be a deliberate attempt by the malware author to plant fraudulent evidence and mislead investigators.[27] The initial infection case of the malware has not yet been identified[10] or disclosed. There is still no guarantee that systems without Kaspersky Lab solutions can protect themselves from ProjectSauron following its public disclosure.

See also

[edit]

References

[edit]
  1. ^ a b Dockrill, Peter (10 August 2016). "Scientists Just Found an Advanced Form of Malware That's Been Hiding For at Least 5 Years". ScienceAlert. Retrieved 2025-06-28.
  2. ^ Goodin, Dan (August 9, 2016). "Researchers crack open unusually advanced malware that hid for 5 years". Ars Technica.
  3. ^ "'Project Sauron' malware hidden for five years". BBC News. August 9, 2016.
  4. ^ "Why Eugene Kaspersky keeps talking about 'Project Sauron'". CyberScoop. December 1, 2017.
  5. ^ GReAT team 2016, 17. Is this a Windows-only threat? What versions of Windows are targeted?.
  6. ^ Seals, Tara (August 19, 2016). "Project Sauron has Been Spying on Governments for 5 Years". Infosecurity Magazine.
  7. ^ Mott, Nathaniel. "Kaspersky Lab and Symantec Discover "Project Sauron" Malware". Inverse.
  8. ^ a b Eric Auchard (August 8, 2016). "New spyware detected targeting firms in Russia, China: Symantec". Reuters. Retrieved 2025-06-28.{{cite web}}: CS1 maint: url-status (link)
  9. ^ GReAT team 2016, 4. For how long have the attackers been active?.
  10. ^ a b GReAT team 2016, 9. What is the initial infection vector?.
  11. ^ a b GReAT team 2016, 8. What kind of implants does ProjectSauron use?.
  12. ^ a b GReAT team 2016, 11. What C&C infrastructure did the attackers use?.
  13. ^ GReAT team 2016, 2. Who are the victims?.
  14. ^ a b GReAT team 2016, 1. What is ProjectSauron?.
  15. ^ GReAT team 2016, 6. How did you discover this malware?.
  16. ^ a b c GReAT team 2016, 7. How does ProjectSauron operate?.
  17. ^ a b GReAT team 2016, From discovery to detection.
  18. ^ a b "Remsec: Top Level Espionage Platform Covertly Extracts Encrypted Government Comms". kaspersky.es. August 1, 2016. Retrieved 2025-06-28, Key Features: "Script-based flexibility"{{cite web}}: CS1 maint: postscript (link) CS1 maint: url-status (link)
  19. ^ GReAT team 2016, 5. Did the attackers use interesting or advanced techniques?.
  20. ^ GReAT team 2016, 24. Do Kaspersky Lab products detect all variants of this malware?.
  21. ^ a b GReAT team 2016, 10. How were the ProjectSauron implants deployed within the target network?.
  22. ^ a b GReAT team 2016, 12. Does ProjectSauron target isolated (air-gapped) networks?.
  23. ^ GReAT team 2016, 16. Are the attackers using any zero-day vulnerabilities?.
  24. ^ a b GReAT team 2016, 19. What exactly is being stolen from the targeted machines?.
  25. ^ GReAT team 2016, 14. Did ProjectSauron use any special communication methods?.
  26. ^ GReAT team 2016, 18. Were the attackers hunting for specific information?.
  27. ^ a b GReAT team 2016, 20. Have you observed any artifacts indicating who is behind the ProjectSauron APT?.
  28. ^ GReAT team 2016, 21. Is this a nation-state sponsored attack?.

Works cited

[edit]