Commwarrior was particularly effective via the MMS vector it used to infect other phones. It appeared as though it had been sent from a source that was known to the victim, leading even security-conscious users to open the infected message.3 Actually, the message was sent at random to a contact in the sender's address book. Once the message is opened, the virus attempts to install itself on the phone via a SIS file. As it runs, the worm is executed every time the phone is switched on.4
A secondary method of infection is to create a malicious .SIS file on a compromised phone. Once per minute thereafter, the worm attempts to send this file to any phone that has Bluetooth enabled.5
According to Sophos, during installation the program has a one in six chance of displaying the following text:6 "CommWarrior v1.0 (c) 2005 by e10d0r"
"Totally Geek :: Virus Source Code Database". Archived from the original on November 10, 2006. Retrieved August 13, 2012. https://web.archive.org/web/20061110144228/http://www.totallygeek.com/vscdb/index.php?a=s&p=0&vi=l&d=c&i=1155663024c7edb20165f74c8eaabb98924c9fff9b ↩
"SymbOS.Commwarrior.I". Symantec. Archived from the original on December 31, 2006. Retrieved 2012-09-25. https://web.archive.org/web/20061231184915/http://www.symantec.com/security_response/writeup.jsp?docid=2006-052510-4833-99 ↩
"Commwarrior cell phone virus marches on - CNET News". News.cnet.com. Retrieved 2012-09-25. http://news.cnet.com/Commwarrior-cell-phone-virus-marches-on/2100-7349_3-5729695.html ↩
"SymbOS.Commwarrior.I Technical Details". Symantec. Archived from the original on April 2, 2015. Retrieved 2012-09-25. https://web.archive.org/web/20150402122201/http://www.symantec.com/security_response/writeup.jsp?docid=2006-052510-4833-99&tabid=2 ↩