CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Kimsuky HelloDoor / PebbleDash C2 evolution

campaign · campaign:kimsuky-pebbledash-hellodoor-trycloudflare-tunnel-c2-evolution single-source

Kimsuky toolkit evolution documented by Kaspersky GReAT (May 2026): the Rust-based HelloDoor variant of PebbleDash alongside httpMalice, MemLoad, httpTroy, AppleSeed and HappyDoor, with TryCloudflare quick-tunnel and VS Code remote-tunnel C2; South Korea is the main target, and PebbleDash victims include a German defense firm.

Coverage
1
first 2026-05-17 → last 2026-10-21
Latest activity
2026-05-17
Kaspersky: Kimsuky's new PebbleDash backdoors hide C2 behind tunnels and take over hosts through VSCode…
Peak priority
notable
1 notable
Targets
public-sector
sectors: public-sector, defense, healthcare · regions: apac, dach, latam
Sources cited
1
1 hosts

Defender insights

What each entry about Kimsuky HelloDoor / PebbleDash C2 evolution tells a defender to do, newest first.

2026-05-17NOTABLEKaspersky: Kimsuky's new PebbleDash backdoors hide C2 behind tunnels and take over hosts through VSCode Remote Tunnels

Exposure · triage · detection

Relationships explore in graph

Typed, source-stated connections from the entity registry; each edge cites the entry whose reporting establishes it.

attributed to

Story timeline

  1. 2026-05-17Kaspersky: Kimsuky adds Rust-based HelloDoor and httpMalice to its PebbleDash toolkit and takes over hosts through VSCode tunnels and DWAgent
    researchKaspersky: Kimsuky's new PebbleDash backdoors hide C2 behind tunnels and take over hosts through VSCode Remote Tunnels
ATT&CK techniques (26 across 11 tactics)

26 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessPhishing: Spearphishing Attachment
  • ExecutionScheduled Task/Job: Scheduled Task · Command and Scripting Interpreter: PowerShell · Command and Scripting Interpreter: JavaScript · User Execution: Malicious File
  • PersistenceScheduled Task/Job: Scheduled Task · Create or Modify System Process: Windows Service · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • Privilege EscalationScheduled Task/Job: Scheduled Task · Create or Modify System Process: Windows Service · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • StealthMasquerading: Double File Extension · Deobfuscate/Decode Files or Information · System Binary Proxy Execution: Regsvr32 · System Binary Proxy Execution: Rundll32 · Virtualization/Sandbox Evasion: System Checks · Hide Artifacts: Hidden Window · Reflective Code Loading
  • Defense ImpairmentSubvert Trust Controls: Code Signing
  • Credential AccessInput Capture: Keylogging
  • DiscoverySystem Information Discovery · Virtualization/Sandbox Evasion: System Checks
  • CollectionInput Capture: Keylogging · Screen Capture · Archive Collected Data
  • Command and ControlApplication Layer Protocol: Web Protocols · Web Service: Bidirectional Communication · Ingress Tool Transfer · Remote Access Tools · Protocol Tunneling · Encrypted Channel: Symmetric Cryptography
  • ExfiltrationExfiltration Over C2 Channel

Initial Access TA0001

T1566.001Phishing: Spearphishing Attachment×1

Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon User Execution to gain execution. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Execution TA0002

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1059.001Command and Scripting Interpreter: PowerShell×1

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. PowerShell can also be installed on Linux and macOS. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1059.007Command and Scripting Interpreter: JavaScript×1

Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1204.002User Execution: Malicious File×1

An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, .cpl, .reg, and .iso.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Persistence TA0003

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1543.003Create or Modify System Process: Windows Service×1

Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence. When Windows boots up, it starts programs or applications called services that perform background system functions. Windows service configuration information, including the file path to the service's executable or recovery programs/commands, is stored in the Windows Registry.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Privilege Escalation TA0004

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1543.003Create or Modify System Process: Windows Service×1

Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence. When Windows boots up, it starts programs or applications called services that perform background system functions. Windows service configuration information, including the file path to the service's executable or recovery programs/commands, is stored in the Windows Registry.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Stealth TA0005

T1036.007Masquerading: Double File Extension×1

Adversaries may abuse a double extension in the filename as a means of masquerading the true file type. A file name may include a secondary file type extension that may cause only the first extension to be displayed (ex: <code>File.txt.exe</code> may render in some views as just <code>File.txt</code>). However, the second extension is the true file type that determines how the file is opened and executed. The real file extension may be hidden by the operating system in the file browser (ex: explorer.exe), as well as in any software configured using or similar to the system’s policies.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1140Deobfuscate/Decode Files or Information×1

Adversaries may use Obfuscated Files or Information to hide artifacts of an intrusion from analysis. They may require separate mechanisms to decode or deobfuscate that information depending on how they intend to use it. Methods for doing that include built-in functionality of malware or by using utilities present on the system.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1218.010System Binary Proxy Execution: Regsvr32×1

Adversaries may abuse Regsvr32.exe to proxy execution of malicious code. Regsvr32.exe is a command-line program used to register and unregister object linking and embedding controls, including dynamic link libraries (DLLs), on Windows systems. The Regsvr32.exe binary may also be signed by Microsoft.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1218.011System Binary Proxy Execution: Rundll32×1

Adversaries may abuse rundll32.exe to proxy execution of malicious code. Using rundll32.exe, vice executing directly (i.e. Shared Modules), may avoid triggering security tools that may not monitor execution of the rundll32.exe process because of allowlists or false positives from normal operations. Rundll32.exe is commonly associated with executing DLL payloads (ex: <code>rundll32.exe {DLLname, DLLfunction}</code>).

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1497.001Virtualization/Sandbox Evasion: System Checks×1

Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1564.003Hide Artifacts: Hidden Window×1

Adversaries may use hidden windows to conceal malicious activity from the plain sight of users. In some cases, windows that would typically be displayed when an application carries out an operation can be hidden. This may be utilized by system administrators to avoid disrupting user work environments when carrying out administrative tasks.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1620Reflective Code Loading×1

Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads. Reflective loading involves allocating then executing payloads directly within the memory of the process, vice creating a thread or process backed by a file path on disk (e.g., Shared Modules).

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Defense Impairment TA0112

T1553.002Subvert Trust Controls: Code Signing×1

Adversaries may create, acquire, or steal code signing materials to sign their malware or tools. Code signing provides a level of authenticity on a binary from the developer and a guarantee that the binary has not been tampered with. The certificates used during an operation may be created, acquired, or stolen by the adversary. Unlike Invalid Code Signature, this activity will result in a valid signature.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Credential Access TA0006

T1056.001Input Capture: Keylogging×1

Adversaries may log user keystrokes to intercept credentials as the user types them. Keylogging is likely to be used to acquire credentials for new access opportunities when OS Credential Dumping efforts are not effective, and may require an adversary to intercept keystrokes on a system for a substantial period of time before credentials can be successfully captured. In order to increase the likelihood of capturing credentials quickly, an adversary may also perform actions such as clearing browser cookies to force users to reauthenticate to systems.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Discovery TA0007

T1082System Information Discovery×1

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use this information to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions. This behavior is distinct from Local Storage Discovery which is an adversary's discovery of local drive, disks and/or volumes.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1497.001Virtualization/Sandbox Evasion: System Checks×1

Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Collection TA0009

T1056.001Input Capture: Keylogging×1

Adversaries may log user keystrokes to intercept credentials as the user types them. Keylogging is likely to be used to acquire credentials for new access opportunities when OS Credential Dumping efforts are not effective, and may require an adversary to intercept keystrokes on a system for a substantial period of time before credentials can be successfully captured. In order to increase the likelihood of capturing credentials quickly, an adversary may also perform actions such as clearing browser cookies to force users to reauthenticate to systems.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1113Screen Capture×1

Adversaries may attempt to take screen captures of the desktop to gather information over the course of an operation. Screen capturing functionality may be included as a feature of a remote access tool used in post-compromise operations. Taking a screenshot is also typically possible through native utilities or API calls, such as <code>CopyFromScreen</code>, <code>xwd</code>, or <code>screencapture</code>.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1560Archive Collected Data×1

An adversary may compress and/or encrypt data that is collected prior to exfiltration. Compressing the data can help to obfuscate the collected data and minimize the amount of data sent over the network. Encryption can be used to hide information that is being exfiltrated from detection or make exfiltration less conspicuous upon inspection by a defender.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Command and Control TA0011

T1071.001Application Layer Protocol: Web Protocols×1

Adversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1102.002Web Service: Bidirectional Communication×1

Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1105Ingress Tool Transfer×1

Adversaries may transfer tools or other files from an external system into a compromised environment. Tools or files may be copied from an external adversary-controlled system to the victim network through the command and control channel or through alternate protocols such as ftp. Once present, adversaries may also transfer/spread tools between victim devices within a compromised environment (i.e. Lateral Tool Transfer).

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1219Remote Access Tools×1

An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management. Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1572Protocol Tunneling×1

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

T1573.001Encrypted Channel: Symmetric Cryptography×1

Adversaries may employ a known symmetric encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Symmetric encryption algorithms use the same key for plaintext encryption and ciphertext decryption. Common symmetric encryption algorithms include AES, DES, 3DES, Blowfish, and RC4.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Exfiltration TA0010

T1041Exfiltration Over C2 Channel×1

Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.

Evidence: 2026-05-17/kaspersky-great-documents-kimsuky-s-rust-based-hellodoor-and · ATT&CK page ↗

Entries about Kimsuky HelloDoor / PebbleDash C2 evolution (1)

2026-05-17 · view entry permalink →

NOTABLEupdatedNATOB2

Kaspersky: Kimsuky adds Rust-based HelloDoor and httpMalice to its PebbleDash toolkit and takes over hosts through VSCode tunnels and DWAgent

Kaspersky's report covers Kimsuky (also APT43, Ruby Sleet) campaigns whose droppers it detected between August 2025 and February 2026: spear-phishing emails deliver compressed attachments disguised as documents, with lure names carrying a document extension before .jse or .pif (Kaspersky Securelist, 2026-05-14). JSE droppers decode at least two Base64 blobs with JScript into a location such as C:\ProgramData, open the lure, then decode the payload a second time with certutil from a hidden PowerShell window and run it through regsvr32 or rundll32, while the SCR and PIF droppers decrypt theirs with XOR (Kaspersky Securelist, 2026-05-14). HelloDoor, a Rust DLL backdoor first seen in August 2025 that Kaspersky judges early-stage, persists through an HKCU Run value that launches regsvr32 and talks to a C2 hosted through TryCloudflare, which makes the infrastructure behind it hard to trace; httpMalice (version 1.9 over HTTP or HTTPS, version 1.8 over the Dropbox API) persists as a service when elevated and through an HKCU Run value otherwise, profiles the host, captures the screen, uploads archived directories and encrypts its traffic with ChaCha20 (Kaspersky Securelist, 2026-05-14). MemLoad runs anti-VM checks and reconnaissance, persists through scheduled tasks that run regsvr32 on its DLL every minute, and reflectively loads the RC4-encrypted httpTroy backdoor in memory for long-term access and exfiltration; the AppleSeed Spy variant collects documents, screenshots, keystrokes and the GPKI certificate directory (Kaspersky Securelist, 2026-05-14).

For post-exploitation the group downloads the legitimate VSCode CLI, unpacks it into C:\Users\Public and runs code.exe tunnel, completing the GitHub device-code authorization with its own account so the host then talks to Microsoft-owned servers, or installs DWAgent from C:\ProgramData with a configuration linked to its own account; it also tunnels through Ngrok, and some samples are signed with certificates stolen from South Korean organizations (Kaspersky Securelist, 2026-05-14). Targets are mainly South Korean public and private entities, and PebbleDash victims also include Brazilian defense organizations and a German defense firm (Kaspersky Securelist, 2026-05-14).

Triage: VSCode Remote Tunnels and DWAgent are legitimate remote-access tools; in Kimsuky's use the VSCode CLI is unpacked into C:\Users\Public and started by a script dropper or installer rather than by the user, and DWAgent arrives with a preset configuration from a dropper that unpacks it into C:\ProgramData (Kaspersky Securelist, 2026-05-14).

Our monitoring indicates various strategic updates to the group’s arsenal, including the use of VSCode Tunneling, Cloudflare Quick Tunnels, DWAgent, large language models (LLMs), and the Rust programming language.

Kimsuky obtains initial access to target systems by delivering spear-phishing emails containing malicious attachments disguised as documents.

Since it has limited capabilities and a simplistic communication mechanism, the backdoor is most probably in the early stages of development.

Kimsuky mainly targets South Korean entities. However, PebbleDash attacks were also seen in Brazil and Germany.

Kaspersky Securelist 2026-05-14
Correctionrun 2026-10-21T1148Z-auditactionsaffected_productsbodyclassificationentitiesevidenceheadlineregionssourcessourcing_notesummarytechniquestitle

httpMalice is not an HTTP-only loader but a PebbleDash-based backdoor that talks over HTTP or HTTPS in version 1.9 and through the Dropbox API in version 1.8, MemLoad is the loader that runs anti-VM checks and reconnaissance before reflectively loading httpTroy, and httpTroy is the backdoor for long-term access and data exfiltration (Kaspersky Securelist, 2026-05-14). The report gives observations rather than detection guidance, so detection follows the dropper, persistence and tunnel artifacts it documents (Kaspersky Securelist, 2026-05-14). HelloDoor is judged early-stage, and its TryCloudflare-hosted C2 makes its infrastructure difficult to trace; Kimsuky also tunnels through VSCode Tunneling and Ngrok (Kaspersky Securelist, 2026-05-14). Targets are mainly South Korean, AppleSeed most often government bodies and PebbleDash the defense, military and medical sectors, and PebbleDash victims also include Brazilian defense organizations and a German defense firm over several years (Kaspersky Securelist, 2026-05-14).

research17 May 05:00Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Research1

Source distribution

  • securelist.com1 (100%)