{
	"id": "f3610a84-1b60-49d9-af2e-28cae0cf5ffe",
	"created_at": "2026-10-25T02:54:18.748408Z",
	"updated_at": "2026-11-22T02:19:45.643788Z",
	"deleted_at": null,
	"sha1_hash": "e21048d0fa32d6b2352412b78c023394f91c3c11",
	"title": "Win32/Lethic Botnet Analysis",
	"llm_title": "Win32/Lethic Botnet Analysis",
	"authors": "Shaman Vilen",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 681182,
	"plain_text": "http://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nWin32/Lethic Botnet Analysis\n\nBy Shaman Vilen\n\nPublished: 2015-07-02 · Archived: 2026-10-25 02:36:22 UTC\n\nIntroduction\n\nLethic is a spam botnet consisting of an estimated 210 000 - 310 000 individual machines which are mainly\n\ninvolved in pharmaceutical and replica spam. At the peak of its existence, the botnet was responsible for 8-10% of\n\nall the spam sent worldwide.\n\nAround early January 2010, the botnet was dismantled by Neustar employees, who contacted various Lethic\n\ninternet service providers in a bid to take control of the botnet's command and control servers. This move\n\ntemporarily caused the botnets' spam to decrease to a trickle of its original volume.\n\nBecome a certified reverse engineer!\n\nGet live, hands-on malware analysis training from anywhere, and become a Certified Reverse Engineering\n\nAnalyst.\n\nIn February 2010, the owners of the botnet managed to re-establish control over the botnet, using new command\n\nand control servers located in the United States. The takedown has decreased the spam volume of the botnet,\n\nPage 1 of 6\n\nhttp://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nhowever. As of February 2010, the botnets' amount of spam was down to a third of its original. As of April 2010,\n\nthe botnet has an estimated 1.5% share of the spam market, sending about 2 billion spam messages a day.\n\nThis article presents a view on the malware and its capabilities, how it communicates with the CnC, encryption\n\nscheme used as well as different protection mechanisms to make the malware analyst job harder.\n\nTools\n\nOllyDBG / IDA Pro.\n\nLethic sample (MD5 = 23DE74A6122A8AB3B02EFD3B2C481978, password = infected)\n\nLethic Unpacked ( password = infected)\n\nInfection vector\n\nThis botnet arrives as attachments to spammed messages disguised as notifications from familiar contacts.\n\nBot analysis\n\nI will not talk about the unpacking process because there is no relevant information regarding it. The original\n\nLethic build file is about 17 kb. Not the smallest botnet ever seen, Tinba or Gamarue have lower size but it is a\n\nlow profile botnet with many infections that may be the secret of its longevity.\n\nLet's go, fire up OllyDBG. OK, you are at the entry point of the malware. Looking at the data section, you could\n\nsee some interesting strings like APIs names to be resolved, modules that are going to be loaded, also CnC IP\n\naddress, etc… Just by looking at this dump, you could basically get a whole image about the inner working of this\n\nbot.\n\nThe first thing, it will try to resolve API dynamically using LoadLibrary and GetProcAddress. Put a BP at the RET\n\ninstruction to see the whole import table filled with the functions pointers:\n\nPage 2 of 6\n\nhttp://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\n1. Following it creates a directory in the APPDATA directory under the name of:\n\n\"C:Documents and SettingsAdministratorApplication DataWindowsUpdate\"\n\nThen, it makes a copy of the file under the name of \"MSupdate.exe\" in this directory and deletes the original file.\n\n1. Following, to autostart with windows, it creates two registry keys at:\n\n\"HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon\" under the\n\nname \"Taskman\" which points to the executable file specified above.\n\n1. And, another key under the name of \"Windows Update Manager\" in:\n\n\"HKEY_LOCAL_USERSoftwareMicrosoftWindowsCurrentVersionRun\"\n\n1. Additionally, it modifies the \"shell\" registry entry located at:\n\n\"HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon\" with the\n\nvalue:\n\nPage 3 of 6\n\nhttp://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nexplorer.exe,C:Documents and SettingsAdministratorApplication DataWindowsUpdateMSupdate.exe\n\nNext, it checks whether the operating system is a 32-bit or 64-bit environment by calling IsWoW64Process. For\n\nmy case, I am running a Windows XP 32bits; this is generally done before performing code injection.\n\nProcess Injection\n\nThe code injection method used in Lethic is VirtualAllocEx/WriteProcessMemory /CreateRemoteThread in\n\nexplorer.exe process. To follow debugging at explorer.exe process, you could either replace the first byte of the\n\nbuffer with 0xCC and make OllyDBG a JIT debugger, and when you step through CreateRemoteThread, a new\n\ninstance of OllyDBG will fire up and will attach to your process, then you can restore back the first byte to its\n\noriginal state. On the other hand, you could look at the start address parameter in CreateRemoteThread, start a\n\nnew instance of OllyDBG, and put a BP on it.\n\nOnce you are done from this step, Lethic creates a new mutex name \"VAmazinsdvd010201\" to prevent duplicate\n\nprocess from running in the same machine. Next, it loads some libraries in explorer memory space and right after\n\nthat; it starts preparing communication with the C\u0026C using Winsock APIs.\n\nC\u0026C Communication\n\nAfter it successfully receives data from the CnC, depending on the value of the command.\n\nLet's list and explain what the different commands sent by the C\u0026C can be, and what they do:\n\nAdd Server (0x01): the data includes a public mail server IP address and a port. Lethic then creates a socket\n\nand connects to the said mail server. Upon success, it initializes a new MailServerRecord with ID, the\n\ngiven IP and port, socket, and then inserts the record in cc_hdr-\u003eChain. Now that the record has been\n\nadded to the chain, should any of the following operations on the record fail, Lethic will inform the C\u0026C\n\nserver; and the latter will then send a \"Remove Server\" command to remove the faulty record.\n\nRemove Server (0x02): removes record corresponding to ID from the mail server record chain.\n\nSend Mail (0x03): sends the buffer data to a mail server, via the MailServerRecord pointed to by ID. The\n\nresult is sent back to the C\u0026C server, which in turns decides whether it should set the RecvFeedBack flag\n\nor not.\n\nClean (0x04, 0x05): do some cleaning work, such as freeing the whole MailServerRecords chain, deleting\n\nthe malware installer, and exit.\n\nReserved (0x06), no further operation except for sending the received data back.\n\nAdd Server By Name (0x11), the same as Add Server, the only difference is that a hostname is given\n\ninstead of an IP address.\n\nReceive FeedBack (0x13), a flag that is used to set MailServerRecord.bfbFlag.\n\nIf the received buffer doesn't include any of the aforementioned commands, Lethic checks each record of the\n\nchain. If the bfbFlag is set to TRUE, that means the Send Mail operation was successful, and feedback was\n\nPage 4 of 6\n\nhttp://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nreceived from the mail server. It thus initializes FEEDBACK with the record ID, command, feedback data, and\n\nsize, and sends it all to the C\u0026C server.\n\nIn all aspects, the Zombie acts as a slightly improved mail relay; it forwards received data from the C\u0026C server to\n\nmail servers chosen in a managed list. That is not very efficient, in terms of bandwidth consumption, as compared\n\nto the traditional template-based approach: Indeed here, the C\u0026C server has to send almost as much data as is sent\n\nby each Zombie. Logically, it seems to indicate that Lethic botnets all need to be small to operate smoothly.\n\nFigure 4 shows an example of the spam content.\n\nPage 5 of 6\n\nhttp://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nBecome a certified reverse engineer!\n\nGet live, hands-on malware analysis training from anywhere, and become a Certified Reverse Engineering\n\nAnalyst.\n\nConclusions\n\nLethic is yet another spambot to join the fray. It is unclear what its future holds, and we do not know when it\n\nemerged. However this shows how \"full\" the \"ecosystem\" for spambots is. Lethic's complexity is minimal when\n\ncompared to other spam botnets (no rootkit seen, etc) but it appears effective enough at this time.\n\nSource: http://resources.infosecinstitute.com/win32lethic-botnet-analysis/\n\nPage 6 of 6",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"Malpedia"
	],
	"origins": [
		"web"
	],
	"references": [
		"http://resources.infosecinstitute.com/win32lethic-botnet-analysis/"
	],
	"report_names": [
		"win32lethic-botnet-analysis"
	],
	"threat_actors": [],
	"ts_created_at": 1792896858,
	"ts_updated_at": 1795313985,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/e21048d0fa32d6b2352412b78c023394f91c3c11.pdf",
		"text": "https://archive.orkl.eu/e21048d0fa32d6b2352412b78c023394f91c3c11.txt",
		"img": "https://archive.orkl.eu/e21048d0fa32d6b2352412b78c023394f91c3c11.jpg"
	},
	"iocs": [
		{
			"type": "domain",
			"value": "resources.infosecinstitute.com",
			"count": 7,
			"flags": [
				"in_url_host"
			],
			"some_flags": [
				"in_url_host"
			]
		},
		{
			"type": "md5",
			"value": "23de74a6122a8ab3b02efd3b2c481978",
			"count": 1,
			"flags": [],
			"some_flags": []
		},
		{
			"type": "url",
			"value": "http://resources.infosecinstitute.com/win32lethic-botnet-analysis/",
			"count": 7,
			"flags": [],
			"some_flags": []
		}
	]
}