{"id":30900,"date":"2025-04-29T21:47:55","date_gmt":"2025-04-29T21:47:55","guid":{"rendered":"https:\/\/gridinsoft.com\/blogs\/?p=30900"},"modified":"2025-04-29T21:47:55","modified_gmt":"2025-04-29T21:47:55","slug":"pe32-ransomware","status":"publish","type":"post","link":"https:\/\/gridinsoft.com\/blogs\/pe32-ransomware\/","title":{"rendered":"PE32 Ransomware"},"content":{"rendered":"

PE32 Ransomware is a recently discovered malware strain<\/strong> that encrypts your files and asks for payment to unlock them. Victims can recognize the files by the sample-specific extension (.pe32), with them becoming inaccessible in normal ways. This malware caught researchers\u2019 eye particularly for using Telegram as a platform for ransom payment negotiations, which is unusual for such malware.<\/p>\n

PE32 Ransomware Overview<\/h2>\n

Cybersecurity researchers have discovered and investigated<\/a> a new ransomware-type threat. PE32 Ransomware encrypts victims\u2019 files and demands payment for decryption while threatening to leak stolen data. Unlike more infamous ransomware families like LockBit<\/a> or Conti<\/a>, which we have separate posts about, PE32 is marked by its immature design and poor security practices<\/strong>. And nonetheless, it remains a significant threat, as it is still able to encrypt the files and disrupt system operations.<\/p>\n

It targets both individual users and corporate environments, with ransom demands ranging from $700 to $7,000 for individual machines or servers and $10,000 to 2 Bitcoin (BTC) for corporate targets. Its most distinctive feature is its reliance on the Telegram Bot API for command and control (C2) communication<\/strong>, a departure from the covert HTTP or DNS methods used by traditional ransomware. This choice, combined with its chaotic behavior, makes PE32 a truly unique case study in the evolving ransomware landscape.<\/p>\n

Detailed PE32 Ransomware Analysis<\/h2>\n

PE32 Ransomware operates in a manner that is both non-obvious and confusing, often defying the logical patterns seen in more refined malware. Its behavior is described as noisy and chaotic, making it easier to detect but challenging to analyze due to its erratic execution. The ransomware encrypts files indiscriminately, targeting everything in its path<\/strong>, including files with little to no value, such as Chrome language files, GIFs, or CSS files. This lack of selectivity underscores its poorly designed logic, as it wastes resources on data that offers no leverage for extortion.<\/p>\n

The ransomware\u2019s execution begins with a simple prompt, after which it rapidly encrypts files, focusing on visible folders like the Desktop. It creates a directory named \u201cC:\\PE32-KEY\u201d containing files such as \u201ccontext.pe32c,\u201d \u201clock.pe32,\u201d \u201cpe32lockfile.lock,\u201d \u201cID,\u201d and \u201cREADME.txt\u201d<\/strong>. Encrypted files are appended with the \u201c.pe32s\u201d extension, marking them as inaccessible. PE32 also drops marker files like \u201cpe32lockfile.lock\u201d in every encrypted folder, to indicate completion, but this triggers false positives in detection systems, complicating analysis. Additionally, it initiates disk repair processes by triggering chkdsk.exe via \u201cC:\\bootTel.dat,\u201d which can destabilize the system further.<\/p>\n

\"PE32-KEY
PE32-KEY folder<\/figcaption><\/figure>\n

From a technical perspective, PE32 relies on standard Windows libraries, including ntdll.dll, kernel32.dll, crypt32.dll, bcrypt.dll, and schannel.dll<\/strong>, to handle operations like TLS\/SSL communication for its Telegram-based C2 channel. Its encryption process is fast, with reported cycles labeled as UltraFast, Fast, and Slow, and it collects system information such as the computer\u2019s GUID, hostname, software policy settings, and supported languages.<\/p>\n

This data collection is likely used to avoid infecting systems in specific regions, however, this contradicts the general logic of the ransomware operation, or rather its absence. Also, some functions within the malware appear to serve no practical purpose, contributing to its illogical behavior. For instance, certain code segments suggest conditional logic, but they do not meaningfully alter the ransomware\u2019s operation, just adding to its confusing nature.<\/p>\n

Command and Control Communication<\/h3>\n

PE32 Ransomware\u2019s command and control<\/a> (C2) communication is a standout feature, relying entirely on the Telegram Bot API<\/strong>. Unlike traditional ransomware, which uses encrypted HTTP, DNS, or custom servers to communicate covertly, PE32 sends all commands and data through Telegram, with no DNS or HTTP requests involved.<\/p>\n

The bot token, a critical component for accessing the Telegram API, is hardcoded into the malware\u2019s code, exposing a significant vulnerability. Just imagine the faces of ransomware operators after Telegram blocks their bot. Moreover, this lack of obfuscation means that anyone who extracts the token can interact with the bot, potentially spamming it, issuing commands, or disrupting its operations.<\/p>\n

The use of Telegram as a C2 channel has several implications. On one hand, it simplifies deployment for attackers, as they do not need to maintain a dedicated server infrastructure. On the other hand, it introduces significant risks. Security researchers or malicious actors can use tools like Matkap (Matkap Tool) to abuse the exposed bot token, leading to potential denial-of-service attacks<\/a> or unauthorized access.<\/p>\n

Additionally, Telegram\u2019s infrastructure is more traceable than Darknet-based<\/a> C2 servers, making it easier for law enforcement or security teams to monitor communications. This \u201cunhidden\u201d approach contrasts sharply with the stealth typically employed by ransomware.<\/p>\n

Ransom Note Overview<\/h3>\n

The ransom note is located in the \u201cC:\\PE32-KEY\\README.txt\u201d file and is notably unconventional. Unlike traditional ransomware, which often directs victims to darknet sites or encrypted communication platforms, PE32 instructs victims to contact the attackers via Telegram, with a backup Gmail address provided<\/strong>.<\/p>\n

\"Ransom
PE32 ransom note<\/figcaption><\/figure>\n

This approach is out of the box, as it leverages public, widely accessible platforms rather than obscure channels. The note typically outlines the ransom demands, emphasizing the dual threat of file encryption and potential data leakage if payment is not made.<\/p>\n

The use of Telegram and Gmail makes the ransom process more accessible for attackers, as they can easily monitor communications. However, it also increases their exposure, as these platforms can be monitored or blocked by security teams.<\/p>\n

How to Remove PE32 Ransomware?<\/h2>\n

Although PE32 Ransomware cannot be called very careful in terms of its operation, it nevertheless fulfills its main function. So, removing PE32 Ransomware requires careful action to prevent further damage. Reputable anti-malware software, such as GridinSoft Anti-Malware, is recommended for detecting and eliminating the ransomware. Next, you need to reboot the device into Safe Mode with networking<\/strong> and run the anti-malware solution. It will update its databases and perform a scan, thereby finding and removing all threats.<\/p>\n

\"PE32<\/a><\/p>\n

Manual removal is strongly discouraged due to the complexity of ransomware and the risk of incomplete removal, which could allow the malware to persist or reinfect the system. Before restoring any backups or accessing encrypted files, it is critical to ensure the ransomware is fully removed to avoid encrypting recovered data. After removal, users should scan their systems thoroughly to confirm the absence of residual threats.<\/p>\n

Can I Recover Files?<\/h2>\n

Unfortunately, recovering files encrypted by PE32 Ransomware is challenging without the attackers\u2019 decryption key. As for now, no known decryption tools are currently available for PE32<\/strong>. Paying the ransom is not advisable, as there first is no guarantee that attackers will provide the decryption key, and it may encourage further demands.<\/p>\n

The most effective recovery method is restoring files from backups. If backups were maintained and stored in separate locations, such as remote servers or unplugged storage devices, users can recover their data after removing the ransomware. In the absence of backups, third-party data recovery tools may offer limited assistance if encrypted files were partially overwritten, but success is not guaranteed.<\/p>\n","protected":false},"excerpt":{"rendered":"

PE32 Ransomware is a recently discovered malware strain that encrypts your files and asks for payment to unlock them. Victims can recognize the files by the sample-specific extension (.pe32), with them becoming inaccessible in normal ways. This malware caught researchers\u2019 eye particularly for using Telegram as a platform for ransom payment negotiations, which is unusual […]<\/p>\n","protected":false},"author":7,"featured_media":30916,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[17,4],"tags":[55],"class_list":{"0":"post-30900","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-labs","8":"category-tips-tricks","9":"tag-ransomware"},"featured_image_src":"https:\/\/gridinsoft.com\/blogs\/wp-content\/uploads\/2025\/04\/GS_BLOG_PE32-Ransomware-The-Chaotic-Telegram-Dependent-File-Locker_1280x674.webp","author_info":{"display_name":"Stephanie Adlam","author_link":"https:\/\/gridinsoft.com\/blogs\/author\/adlam\/"},"_links":{"self":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/comments?post=30900"}],"version-history":[{"count":15,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30900\/revisions"}],"predecessor-version":[{"id":30949,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30900\/revisions\/30949"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/media\/30916"}],"wp:attachment":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/media?parent=30900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/categories?post=30900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/tags?post=30900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}