{
	"id": "5076f4e4-1733-4e0d-8f67-40aa693b1c0d",
	"created_at": "2026-04-06T03:37:08.038096Z",
	"updated_at": "2026-04-10T03:20:43.034793Z",
	"deleted_at": null,
	"sha1_hash": "a9d97b3fe8f7100a22350db5fce875d8609c6816",
	"title": "Trojan.Volgmer | Symantec",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 76144,
	"plain_text": "Trojan.Volgmer | Symantec\r\nArchived: 2026-04-06 03:20:32 UTC\r\nThe Wayback Machine - https://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nDiscovered: August 18, 2014\r\nUpdated: August 20, 2014 2:45:26 PM\r\nType: Trojan\r\nInfection Length: Varies\r\nSystems Affected: Windows\r\nTrojan.Volgmer is a Trojan horse that opens a back door on the compromised computer.\r\nAntivirus Protection Dates\r\nInitial Rapid Release version August 18, 2014 revision 008\r\nLatest Rapid Release version January 25, 2018 revision 019\r\nInitial Daily Certified version August 18, 2014 revision 019\r\nLatest Daily Certified version January 26, 2018 revision 002\r\nInitial Weekly Certified release date August 20, 2014\r\nClick here for a more detailed description of Rapid Release and Daily Certified virus definitions.\r\nWriteup By: Junnosuke Yagi\r\nDiscovered: August 18, 2014\r\nUpdated: August 20, 2014 2:45:26 PM\r\nType: Trojan\r\nInfection Length: Varies\r\nSystems Affected: Windows\r\nOnce executed, the Trojan creates the following files:\r\n%System%\\[RANDOM FILE NAME].dll\r\n%Temp%\\pdm.bat\r\nIt then creates a service with the following properties:\r\nDisplay Name: [RANDOM SERVICE NAME]\r\nImage Path: %System%\\svchost.exe -k LocalSystems\r\nDescription: The [RANDOM SERVICE NAME] is an essential service for management of Windows\r\nSystem. If the service is stopped or disabled, Windows will be able to damaged seriously.\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 1 of 6\n\nNote: [RANDOM SERVICE NAME] may be composed of the following words:\r\nApplication\r\nBackground\r\nControl\r\nDesktop\r\nExtension\r\nFunction\r\nGroup\r\nHost\r\nIntelligent\r\nKey\r\nLayer\r\nMultimedia\r\nNetwork\r\nOperation\r\nPortable\r\nQuality\r\nRemote\r\nSecurity\r\nTCP/IP\r\nUser Profile\r\nVolume\r\nWindows\r\nDevice\r\nUpd\r\nService\r\nManagement\r\nManager\r\nEnum\r\nFor example: Control Portable Volume Manager or Background Operation Windows Manager\r\nThe Trojan then creates the following registry subkey to register itself as a service:\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\[RANDOM FILE NAME]\r\nIt also creates the following registry entries:\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Security\\\"f0012345-2a9c-bdf8-\r\n345d-345d67b542a1\" = \"[HEXADECIMAL VALUE]\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Security\\\"125463f3-2a9c-bdf0-\r\nd890-5a98b08d8898\" = \"[HEXADECIMAL VALUE]\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"Service\" = \"[RANDOM FILE NAME]\"\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 2 of 6\n\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"Legacy\" = \"1\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"DeviceDesc\" = \"[RANDOM SERVICE NAME]\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"ConfigFlags\" = \"0\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"ClassGUID\" = \"{8ECC055D-047F-11D1-A537-0000F8753ED1}\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\0000\\\"Class\" = \"LegacyDriver\"\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\Root\\LEGACY_[RANDOM FILE\r\nNAME]\\\"NextInstance\" = \"1\"\r\nNext, the Trojan connects to one or more of the following IP addresses on TCP port 8080 or 8088:\r\n113.28.244.194\r\n116.48.145.179\r\n186.116.9.20\r\n193.28.91.232\r\n199.15.234.120\r\n200.42.69.133\r\n220.128.131.251\r\n24.242.176.130\r\n78.93.190.70\r\n89.190.188.42\r\nThe Trojan then opens a back door on the compromised computer, allowing an attacker to perform the following\r\nactions:\r\nGather system information\r\nDownload and execute files\r\nUpdate service registry key\r\nUpload files\r\nGathered system information may include the following:\r\nComputer name\r\nIP address\r\nDrive name and serial number\r\nLocale information\r\nTCP connection state\r\nOperating system version\r\nProcess list\r\nRecommendations\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 3 of 6\n\nSymantec Security Response encourages all users and administrators to adhere to the following basic security\r\n\"best practices\":\r\nUse a firewall to block all incoming connections from the Internet to services that should not be publicly\r\navailable. By default, you should deny all incoming connections and only allow services you explicitly\r\nwant to offer to the outside world.\r\nEnforce a password policy. Complex passwords make it difficult to crack password files on compromised\r\ncomputers. This helps to prevent or limit damage when a computer is compromised.\r\nEnsure that programs and users of the computer use the lowest level of privileges necessary to complete a\r\ntask. When prompted for a root or UAC password, ensure that the program asking for administration-level\r\naccess is a legitimate application.\r\nDisable AutoPlay to prevent the automatic launching of executable files on network and removable drives,\r\nand disconnect the drives when not required. If write access is not required, enable read-only mode if the\r\noption is available.\r\nTurn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit\r\naccess. Disable anonymous access to shared folders. Grant access only to user accounts with strong\r\npasswords to folders that must be shared.\r\nTurn off and remove unnecessary services. By default, many operating systems install auxiliary services\r\nthat are not critical. These services are avenues of attack. If they are removed, threats have less avenues of\r\nattack.\r\nIf a threat exploits one or more network services, disable, or block access to, those services until a patch is\r\napplied.\r\nAlways keep your patch levels up-to-date, especially on computers that host public services and are\r\naccessible through the firewall, such as HTTP, FTP, mail, and DNS services.\r\nConfigure your email server to block or remove email that contains file attachments that are commonly\r\nused to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.\r\nIsolate compromised computers quickly to prevent threats from spreading further. Perform a forensic\r\nanalysis and restore the computers using trusted media.\r\nTrain employees not to open attachments unless they are expecting them. Also, do not execute software\r\nthat is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised\r\nWeb site can cause infection if certain browser vulnerabilities are not patched.\r\nIf Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the\r\ndevice's visibility is set to \"Hidden\" so that it cannot be scanned by other Bluetooth devices. If device\r\npairing must be used, ensure that all devices are set to \"Unauthorized\", requiring authorization for each\r\nconnection request. Do not accept applications that are unsigned or sent from unknown sources.\r\nFor further information on the terms used in this document, please refer to the Security Response glossary.\r\nWriteup By: Junnosuke Yagi\r\nDiscovered: August 18, 2014\r\nUpdated: August 20, 2014 2:45:26 PM\r\nType: Trojan\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 4 of 6\n\nInfection Length: Varies\r\nSystems Affected: Windows\r\nYou may have arrived at this page either because you have been alerted by your Symantec product about this risk,\r\nor you are concerned that your computer has been affected by this risk.\r\nBefore proceeding further we recommend that you run a full system scan . If that does not resolve the problem\r\nyou can try one of the options available below.\r\nFOR NORTON USERS\r\nIf you are a Norton product user, we recommend you try the following resources to remove this risk.\r\nRemoval Tool\r\nRun Norton Power Eraser (NPE)\r\nNorton Power Eraser did not remove this risk\r\nIf you have an infected Windows system file, you may need to replace it using the Windows installation CD .\r\nHow to reduce the risk of infection\r\nThe following resources provide further information and best practices to help reduce the risk of infection.\r\nOperating system updates to fix vulnerabilities\r\nFile sharing protection\r\nDisable Autorun (CD/USB)\r\nBest practices for instant messaging\r\nBest practices for browsing the Web\r\nBest practices for email\r\nFOR BUSINESS USERS\r\nIf you are a Symantec business product user, we recommend you try the following resources to remove this risk.\r\nIdentifying and submitting suspect files\r\nSubmitting suspicious files to Symantec allows us to ensure that our protection capabilities keep up with the ever-changing threat landscape. Submitted files are analyzed by Symantec Security Response and, where necessary,\r\nupdated definitions are immediately distributed through LiveUpdate™ to all Symantec end points. This ensures\r\nthat other computers nearby are protected from attack. The following resources may help in identifying suspicious\r\nfiles for submission to Symantec.\r\nLocate a sample of a threat\r\nSubmit a suspicious file to Symantec\r\nRemoval Tool\r\nRun Symantec Power Eraser in Symantec Help (SymHelp)\r\nAbout Symantec Power Eraser\r\nSymantec Power Eraser User Guide\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 5 of 6\n\nIf you have an infected Windows system file, you may need to replace it using the Windows installation CD .\r\nHow to reduce the risk of infection\r\nThe following resource provides further information and best practices to help reduce the risk of infection.\r\nProtecting your business network\r\nMANUAL REMOVAL\r\nThe following instructions pertain to all current Symantec antivirus products.\r\n1. Performing a full system scan\r\nHow to run a full system scan using your Symantec product\r\n2. Restoring settings in the registry\r\nMany risks make modifications to the registry, which could impact the functionality or performance of the\r\ncompromised computer. While many of these modifications can be restored through various Windows\r\ncomponents, it may be necessary to edit the registry. See in the Technical Details of this writeup for information\r\nabout which registry keys were created or modified. Delete registry subkeys and entries created by the risk and\r\nreturn all modified registry entries to their previous values.\r\nWriteup By: Junnosuke Yagi\r\nSource: https://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nhttps://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2\r\nPage 6 of 6",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://web.archive.org/web/20181126143456/https://www.symantec.com/security-center/writeup/2014-081811-3237-99?tabid=2"
	],
	"report_names": [
		"2014-081811-3237-99?tabid=2"
	],
	"threat_actors": [],
	"ts_created_at": 1775446628,
	"ts_updated_at": 1775791243,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/a9d97b3fe8f7100a22350db5fce875d8609c6816.pdf",
		"text": "https://archive.orkl.eu/a9d97b3fe8f7100a22350db5fce875d8609c6816.txt",
		"img": "https://archive.orkl.eu/a9d97b3fe8f7100a22350db5fce875d8609c6816.jpg"
	}
}