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

Jade Sleet

actor · actor:jade-sleet single-source

Sekoia and Kudelski Security assess this is one of two clusters (with CryptoCore) that APT38 split into between 2018 and 2023; exclusively financially motivated, focused on cryptocurrency, Web3 and blockchain targets (Sekoia/Kudelski Security, 2026-09-07). SentinelLabs (2026-09-18) names TraderTraitor / UNC4899 / PUKCHONG as aliases of Jade Sleet in its FLATROOF/ROOFDECK backdoor reporting.

Aliases: TraderTraitor, UNC4899, PUKCHONG

Coverage
3
first 2026-09-08 → last 2026-10-09
Latest activity
2026-10-09
SentinelLabs: the same DPRK backdoors from a $292M crypto theft resurface on a victim with no crypto ties, in…
Peak priority
notable
3 notable
Targets
finance
sectors: finance
Sources cited
11
9 hosts
2026-09-083 appearances2026-09-29

Defender insights

What each entry about Jade Sleet tells a defender to do, newest first.

2026-09-21NOTABLESentinelLabs: the same DPRK backdoors from a $292M crypto theft resurface on a victim with no crypto ties, in a campaign that uses poisoned Terraform lockfiles

Triage

2026-09-29NOTABLECompromised security appliances, not a key theft, gave the attacker a path to Bitget's wallet server

Detection

2026-09-08NOTABLEA Swiss research lab co-publishes the DPRK actor-tracking update: two nominally-espionage clusters rented commodity ransomware in the same window

Story timeline

  1. 2026-09-29Bitget: an attacker compromised two third-party security appliances, moved laterally to the wallet job server and stole $388M in one of 2026's largest crypto-exchange hacks
    active-threatsCompromised security appliances, not a key theft, gave the attacker a path to Bitget's wallet server
  2. 2026-09-21TraderTraitor (Jade Sleet) backdoors resurface on a non-cryptocurrency IT-services firm in a campaign that delivers malware through weaponized Terraform provider lockfiles, resolving C2 through a Nostr-relay dead drop
    active-threatsSentinelLabs: the same DPRK backdoors from a $292M crypto theft resurface on a victim with no crypto ties, in a campaign that uses poisoned Terraform lockfiles
  3. 2026-09-08Sekoia and Kudelski Security split the 'Lazarus umbrella' into six named DPRK clusters, and document two of them adopting commodity ransomware-as-a-service within two months of each other
    researchA Swiss research lab co-publishes the DPRK actor-tracking update: two nominally-espionage clusters rented commodity ransomware in the same window
ATT&CK techniques (37 across 13 tactics)

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

  • Initial AccessValid Accounts · Supply Chain Compromise: Compromise Software Supply Chain
  • ExecutionCommand and Scripting Interpreter · Command and Scripting Interpreter: Unix Shell · Command and Scripting Interpreter: Python · User Execution: Malicious File
  • PersistenceValid Accounts · Server Software Component: Web Shell · Event Triggered Execution: Unix Shell Configuration Modification
  • Privilege EscalationProcess Injection: Process Hollowing · Valid Accounts · Event Triggered Execution: Unix Shell Configuration Modification
  • StealthObfuscated Files or Information · Obfuscated Files or Information: Embedded Payloads · Obfuscated Files or Information: Encrypted/Encoded File · Masquerading: Match Legitimate Resource Name or Location · Masquerading: Masquerade File Type · Process Injection: Process Hollowing · Indicator Removal: File Deletion · Valid Accounts
  • Defense ImpairmentSubvert Trust Controls: Gatekeeper Bypass · Subvert Trust Controls: Code Signing
  • Credential AccessSteal Web Session Cookie · Unsecured Credentials · Unsecured Credentials: Shell History · Credentials from Password Stores: Keychain · Credentials from Password Stores: Windows Credential Manager
  • DiscoverySystem Information Discovery · Browser Information Discovery
  • Lateral MovementLateral Tool Transfer
  • CollectionData from Local System · Clipboard Data · Automated Collection · Archive Collected Data: Archive via Utility
  • Command and ControlFallback Channels · Application Layer Protocol: Web Protocols · Web Service: Dead Drop Resolver
  • ExfiltrationExfiltration Over Web Service
  • ImpactData Encrypted for Impact · Data Manipulation: Stored Data Manipulation · Data Manipulation: Transmitted Data Manipulation · Financial Theft

Initial Access TA0001

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1195.002Supply Chain Compromise: Compromise Software Supply Chain×1

Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise. Supply chain compromise of software can take place in a number of ways, including manipulation of the application source code, manipulation of the update/distribution mechanism for that software, or replacing compiled releases with a modified version.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Execution TA0002

T1059Command and Scripting Interpreter×1

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1059.004Command and Scripting Interpreter: Unix Shell×1

Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1059.006Command and Scripting Interpreter: Python×1

Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the <code>python.exe</code> interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · 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-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Persistence TA0003

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1505.003Server Software Component: Web Shell×1

Adversaries may backdoor web servers with web shells to establish persistent access to systems. A Web shell is a Web script that is placed on an openly accessible Web server to allow an adversary to access the Web server as a gateway into a network. A Web shell may provide a set of functions to execute or a command-line interface on the system that hosts the Web server.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1546.004Event Triggered Execution: Unix Shell Configuration Modification×1

Adversaries may establish persistence through executing malicious commands triggered by a user’s shell. User Unix Shells execute several configuration scripts at different points throughout the session based on events. For example, when a user opens a command-line interface or remotely logs in (such as via SSH) a login shell is initiated. The login shell executes scripts from the system (<code>/etc</code>) and the user’s home directory (<code>~/</code>) to configure the environment. All login shells on a system use /etc/profile when initiated. These configuration scripts run at the permission level of their directory and are often used to set environment variables, create aliases, and customize the user’s environment. When the shell exits or terminates, additional shell scripts are executed to ensure the shell exits appropriately.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Privilege Escalation TA0004

T1055.012Process Injection: Process Hollowing×1

Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1546.004Event Triggered Execution: Unix Shell Configuration Modification×1

Adversaries may establish persistence through executing malicious commands triggered by a user’s shell. User Unix Shells execute several configuration scripts at different points throughout the session based on events. For example, when a user opens a command-line interface or remotely logs in (such as via SSH) a login shell is initiated. The login shell executes scripts from the system (<code>/etc</code>) and the user’s home directory (<code>~/</code>) to configure the environment. All login shells on a system use /etc/profile when initiated. These configuration scripts run at the permission level of their directory and are often used to set environment variables, create aliases, and customize the user’s environment. When the shell exits or terminates, additional shell scripts are executed to ensure the shell exits appropriately.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Stealth TA0005

T1027Obfuscated Files or Information×1

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1027.009Obfuscated Files or Information: Embedded Payloads×1

Adversaries may embed payloads within other files to conceal malicious content from defenses. Otherwise seemingly benign files (such as scripts and executables) may be abused to carry and obfuscate malicious payloads and content. In some cases, embedded payloads may also enable adversaries to Subvert Trust Controls by not impacting execution controls such as digital signatures and notarization tickets.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1027.013Obfuscated Files or Information: Encrypted/Encoded File×1

Adversaries may encrypt or encode files to obfuscate strings, bytes, and other specific patterns to impede detection. Encrypting and/or encoding file content aims to conceal malicious artifacts within a file used in an intrusion. Many other techniques, such as Software Packing, Steganography, and Embedded Payloads, share this same broad objective. Encrypting and/or encoding files could lead to a lapse in detection of static signatures, only for this malicious content to be revealed (i.e., Deobfuscate/Decode Files or Information) at the time of execution/use.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1036.005Masquerading: Match Legitimate Resource Name or Location×1

Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1036.008Masquerading: Masquerade File Type×1

Adversaries may masquerade malicious payloads as legitimate files through changes to the payload's formatting, including the file’s signature, extension, icon, and contents. Various file types have a typical standard format, including how they are encoded and organized. For example, a file’s signature (also known as header or magic bytes) is the beginning bytes of a file and is often used to identify the file’s type. For example, the header of a JPEG file, is <code> 0xFF 0xD8</code> and the file extension is either `.JPE`, `.JPEG` or `.JPG`.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1055.012Process Injection: Process Hollowing×1

Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1070.004Indicator Removal: File Deletion×1

Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Defense Impairment TA0112

T1553.001Subvert Trust Controls: Gatekeeper Bypass×1

Adversaries may modify file attributes and subvert Gatekeeper functionality to evade user prompts and execute untrusted programs. Gatekeeper is a set of technologies that act as layer of Apple’s security model to ensure only trusted applications are executed on a host. Gatekeeper was built on top of File Quarantine in Snow Leopard (10.6, 2009) and has grown to include Code Signing, security policy compliance, Notarization, and more. Gatekeeper also treats applications running for the first time differently than reopened applications.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

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-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Credential Access TA0006

T1539Steal Web Session Cookie×1

An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials. Web applications and services often use session cookies as an authentication token after a user has authenticated to a website.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1552Unsecured Credentials×1

Adversaries may search compromised systems to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on a system, including plaintext files (e.g. Shell History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys).

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1552.003Unsecured Credentials: Shell History×1

Adversaries may search the command history on compromised systems for insecurely stored credentials.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1555.001Credentials from Password Stores: Keychain×1

Adversaries may acquire credentials from Keychain. Keychain (or Keychain Services) is the macOS credential management system that stores account names, passwords, private keys, certificates, sensitive application data, payment data, and secure notes. There are three types of Keychains: Login Keychain, System Keychain, and Local Items (iCloud) Keychain. The default Keychain is the Login Keychain, which stores user passwords and information. The System Keychain stores items accessed by the operating system, such as items shared among users on a host. The Local Items (iCloud) Keychain is used for items synced with Apple’s iCloud service.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1555.004Credentials from Password Stores: Windows Credential Manager×1

Adversaries may acquire credentials from the Windows Credential Manager. The Credential Manager stores credentials for signing into websites, applications, and/or devices that request authentication through NTLM or Kerberos in Credential Lockers (previously known as Windows Vaults).

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · 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-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1217Browser Information Discovery×1

Adversaries may enumerate information about browsers to learn more about compromised environments. Data saved by browsers (such as bookmarks, accounts, and browsing history) may reveal a variety of personal information about users (e.g., banking sites, relationships/interests, social media, etc.) as well as details about internal network resources such as servers, tools/dashboards, or other related infrastructure.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Lateral Movement TA0008

T1570Lateral Tool Transfer×1

Adversaries may transfer tools or other files between systems in a compromised environment. Once brought into the victim environment (i.e., Ingress Tool Transfer) files may then be copied from one system to another to stage adversary tools or other files over the course of an operation.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Collection TA0009

T1005Data from Local System×1

Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1115Clipboard Data×1

Adversaries may collect data stored in the clipboard from users copying information within or between applications.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1119Automated Collection×1

Once established within a system or network, an adversary may use automated techniques for collecting internal data. Methods for performing this technique could include use of a Command and Scripting Interpreter to search for and copy information fitting set criteria such as file type, location, or name at specific time intervals.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1560.001Archive Collected Data: Archive via Utility×1

Adversaries may use utilities to compress and/or encrypt collected data prior to exfiltration. Many utilities include functionalities to compress, encrypt, or otherwise package data into a format that is easier/more secure to transport.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Command and Control TA0011

T1008Fallback Channels×1

Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

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-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

T1102.001Web Service: Dead Drop Resolver×1

Adversaries may use an existing, legitimate external Web service to host information that points to additional command and control (C2) infrastructure. Adversaries may post content, known as a dead drop resolver, on Web services with embedded (and often obfuscated/encoded) domains or IP addresses. Once infected, victims will reach out to and be redirected by these resolvers.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Exfiltration TA0010

T1567Exfiltration Over Web Service×1

Adversaries may use an existing, legitimate external Web service to exfiltrate data rather than their primary command and control channel. Popular Web services acting as an exfiltration mechanism may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to compromise. Firewall rules may also already exist to permit traffic to these services.

Evidence: 2026-09-21/tradertraitor-terraform-lockfile-nostr-dead-drop · ATT&CK page ↗

Impact TA0040

T1486Data Encrypted for Impact×1

Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.

Evidence: 2026-09-08/sekoia-kudelski-dprk-lazarus-umbrella-six-cluster-split · ATT&CK page ↗

T1565.001Data Manipulation: Stored Data Manipulation×1

Adversaries may insert, delete, or manipulate data at rest in order to influence external outcomes or hide activity, thus threatening the integrity of the data. By manipulating stored data, adversaries may attempt to affect a business process, organizational understanding, and decision making.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1565.002Data Manipulation: Transmitted Data Manipulation×1

Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data. By manipulating transmitted data, adversaries may attempt to affect a business process, organizational understanding, and decision making.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1657Financial Theft×2

Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims. Financial theft is the ultimate objective of several popular campaign types including extortion by ransomware, business email compromise (BEC) and fraud, "pig butchering," bank hacking, and exploiting cryptocurrency networks.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · 2026-09-08/sekoia-kudelski-dprk-lazarus-umbrella-six-cluster-split · ATT&CK page ↗

Entries about Jade Sleet (3)

2026-09-21 · view entry permalink →

NOTABLEupdatedNATOB2

TraderTraitor (Jade Sleet) backdoors resurface on a non-cryptocurrency IT-services firm in a campaign that delivers malware through weaponized Terraform provider lockfiles, resolving C2 through a Nostr-relay dead drop

SentinelLabs hunted its telemetry for the FLATROOF (also known as macOS.Gaslight) and ROOFDECK macOS backdoors first disclosed in April 2026's USD 292 million LayerZero/KelpDAO cryptocurrency theft, and found an unrelated victim carrying the same implants: a small India-based IT-services provider with no cryptocurrency exposure, compromised through a single Apple Silicon MacBook belonging to a DevOps engineer (SentinelOne SentinelLabs, 2026-09-18). The lure follows DPRK's established "Contagious Interview" pattern: fake job-interview GitHub repositories themed as infrastructure-engineering coding challenges each carry a weaponized .terraform.lock.hcl pointing to a typosquatted, attacker-controlled Terraform provider registry impersonating HashiCorp's own naming. Because Terraform treats the lockfile's declared provider source as authoritative, running terraform init against the poisoned lockfile causes Terraform itself to download and execute the attacker's provider module in place of the genuine HashiCorp one. SentinelLabs cannot prove how this victim's backdoors were delivered: both were on disk by March 18, and the victim cloned a lure repository only on April 13 (SentinelOne SentinelLabs, 2026-09-18).

On the victim host, both backdoors sat dormant on disk from March 18 to March 29, 2026, then launched the moment the developer opened a specific Cursor IDE workspace: the Cursor process itself spawned both implants directly, which began beaconing to their command-and-control servers within two seconds, before FLATROOF stripped the macOS quarantine attribute from ROOFDECK and set its executable bit moments later, a Gatekeeper bypass. FLATROOF is a Rust ARM64 backdoor supporting shell, kill, upload and stop commands, paired with a Python data-harvesting module that pulls Chrome/Brave/Firefox/Safari data, Terminal history, installed-application lists, ps aux output, system_profiler output and a raw copy of login.keychain-db, exfiltrated via a hardcoded Telegram bot. ROOFDECK is the more capable second-stage implant: on first run it queries a public Nostr relay-status API plus a hardcoded relay list, searches Nostr relays for an operator profile matching a configured public key, and reads that profile's "website" field as its live command-and-control URL, a decentralized dead-drop resolver that survives takedown of any single C2 domain. A third stage later replaced both original implants and beaconed intermittently to a separate C2 until 2026-06-01, the last beacon in SentinelLabs' collected telemetry (SentinelOne SentinelLabs, 2026-09-18).

Triage: developers legitimately run terraform init against new or unfamiliar repositories constantly, so the command itself is not the signal: the discriminator is the lockfile's declared provider source pointing to a domain that is not registry.terraform.io or a known private registry the organization operates.

Unlike the previous high-profile victim, this target was a much smaller organization in the IT services industry.

When the victim runs terraform init with the weaponized lockfile in place, Terraform treats the custom provider as the source of truth, resulting in Terraform downloading and executing the malicious provider modules.

When found, it reads the website field of the profile and uses that as its C2 URL.

SentinelOne / SentinelLabs 2026-09-18

a trojanized Terraform provider that executes malicious code as soon as Terraform loads the provider

Zscaler ThreatLabz 2026-10-08
Correctionrun 2026-09-30T0639Z-auditprioritybodysourcing_notetitleheadlinesummaryevidence

SentinelLabs cannot prove how this victim's backdoors were delivered: both were on disk by March 18 and ran from March 29, while the victim cloned a lure repository only on April 13 (SentinelOne SentinelLabs, 2026-09-18). The weaponized Terraform lockfile is the campaign's documented delivery method for its lure repositories, not this victim's proven initial access (SentinelOne SentinelLabs, 2026-09-18).

Updaterun 2026-10-09T0255Z-intelsummarytechniquesentitiesaffected_productssourcesevidenceverificationsourcing_notebody

Zscaler ThreatLabz reports a July 2026 campaign that it suspects is TraderTraitor, citing substantial overlap in tactics and targeting but no code, infrastructure or cryptographic links sufficient for attribution with high confidence, in which a Go-built Terraform provider that poses as an AWS provider executes malicious code the moment Terraform loads the plugin: it writes a run-once marker in the temporary directory, downloads a Bash loader from a lookalike of a HashiCorp domain, starts it through a detached sh -c child and keeps behaving like a normal provider (Zscaler ThreatLabz, 2026-10-08). The loader runs on macOS, Linux and Windows with a Unix-like shell, picks a payload by operating system and CPU architecture and recovers an encrypted executable appended after a marker in a file named like a web font; on macOS it removes the quarantine attribute and applies an ad-hoc signature (Zscaler ThreatLabz, 2026-10-08). The delivered FLATROOF is a Rust backdoor with Telegram Bot API, GitHub-polling and HTTP-webhook command channels, persistence as a service on Linux, a zlogout entry on macOS and a registry entry on Windows, and Python stealers for browser data, cookies, keychain or Credential Manager entries, shell history and wallet-extension data; it drops ROOFDECK, which finds its server through a local configuration, then an RSA-signed Pastebin dead drop, with Nostr profile metadata only as the fallback, so its order of resolvers differs from the Nostr-first behaviour SentinelLabs describes above (Zscaler ThreatLabz, 2026-10-08). Zscaler does not know how the provider reached the victim, and notes that SentinelLabs independently reported related activity with weaponized Terraform projects (Zscaler ThreatLabz, 2026-10-08).

The telemetry that follows from the provider path is the Terraform provider plugin process making an HTTPS download from a host that is not the Terraform registry, writing a script to the temporary directory and starting it through sh -c; Zscaler advises restricting untrusted Terraform providers, verifying provider checksums and monitoring unexpected process activity (Zscaler ThreatLabz, 2026-10-08).

Builds on: A Swiss research lab co-publishes the DPRK actor-tracking update: two nominally-espionage…

threat21 Sep 04:43Zmulti-sourceOpen finding →

2026-09-29 · view entry permalink →

NOTABLEupdatedNATOB2

Bitget: an attacker compromised two third-party security appliances, moved laterally to the wallet job server and stole $388M in one of 2026's largest crypto-exchange hacks

Cryptocurrency exchange Bitget confirms that, at 18:31 UTC on 2026-09-24, unauthorized transfers occurred from a portion of its hot and warm wallet infrastructure across eleven blockchains: Ethereum, XRP Ledger, TRON, Arbitrum, Optimism, Base, BNB Smart Chain, Avalanche, Algorand, Celestia and Zcash (Bitget, 2026-09-27). Per Bitget's own investigation, the attacker did not steal a private key: "the attacker may have exploited a vulnerability in a third-party security product to potentially obtain high-level internal credentials," then used those credentials "to impersonate authorized activity and send fraudulent withdrawal commands to the wallet system," bypassing existing risk controls (Bitget, 2026-09-27). CEO Gracy Chen described the mechanism directly: "The attacker compromised a critical backend system within our wallet infrastructure, used it to spoof transaction data, and triggered our authorization process to move funds out" (The Hacker News, 2026-09-25). Bitget states private-key compromise was ruled out and cold wallets were unaffected; the vulnerable third-party product's vendor was notified and the affected functionality disabled pending a fix.

Total loss is now estimated at approximately $388M across twelve wallet addresses (Bitget, 2026-09-27), up from the USD 351.6M loss Bitget first reported, the figure TRM Labs uses in its analysis (TRM Labs, 2026-09-25). Bitget says its Protection Fund covers the financial impact (Bitget, 2026-09-27), a fund Bitget sizes at USD 464 million, according to TRM Labs (TRM Labs, 2026-09-25). Customer account balances, deposits and trading were unaffected, and withdrawals, paused at detection, resumed in phases starting with Bitcoin on 2026-09-28. Bitget revoked and reissued internal login credentials, restructured access to highly sensitive systems, now requires multiple approvals for critical operations, and engaged Mandiant and SlowMist for independent forensics (Bitget, 2026-09-27).

Bitget's CEO called North Korean involvement "very likely," based on the team's preliminary investigation linking observed IP addresses to VPN services associated with a North Korean hacking group (TRM Labs, 2026-09-25). TRM Labs, an independent blockchain-forensics firm, reports multiple on-chain overlaps with wallets used to launder earlier North Korean thefts, including Bybit and AFX Bridge, through a laundering network it has not linked to any other group's thefts, so the overlaps point to TraderTraitor: "these onchain links confirm the group laundering these proceeds is the same one used by TraderTraitor in other recent hacks" (TRM Labs, 2026-09-25). TRM is explicit that this stops short of definitive attribution: "TRM has not yet definitively attributed the exploit to North Korea" and "another actor carrying out the theft remains technically possible."

the attacker may have exploited a vulnerability in a third-party security product to potentially obtain high-level internal credentials

Bitget (official incident page) 2026-09-27

The attacker compromised a critical backend system within our wallet infrastructure, used it to spoof transaction data, and triggered our authorization process to move funds out.

Bitget CEO Gracy Chen, via The Hacker News

these onchain links confirm the group laundering these proceeds is the same one used by TraderTraitor in other recent hacks

TRM Labs 2026-09-25

The threat actor deployed a web shell onto the security appliance B and established a Command-and-Control (C2) connection.

Mandiant (Google Cloud)

The earliest malicious activity identified in the available logs dates to August 31.

SlowMist 2026-09-29
Updaterun 2026-09-30T0639Z-auditpriorityupdated_attitleheadlinesummarytechniquessourcesevidencesourcing_notebody

Bitget released the independent investigation reports from Mandiant and SlowMist on 2026-09-30. Both identify the compromise of third-party security products as what enabled access to the wallet environment (Bitget, 2026-09-30). Mandiant's status report states that on 2026-09-24 the attacker "gained unauthorised privileged access to Bitget's third party security appliances A and B", deployed a web shell on appliance B, established a command-and-control connection, and used that persistent access to move laterally to Bitget's production wallet job server and deploy malicious packages (Mandiant, 2026-09-28).

The two reports date different events and label the appliances independently: Mandiant dates the attacker's privileged access to appliances A and B to 2026-09-24 (Mandiant, 2026-09-28), while SlowMist dates the earliest malicious activity in its logs, on a node of its Product A, to 2026-08-31 (SlowMist, 2026-09-29).

SlowMist dates the earliest malicious activity in the available logs to 2026-08-31: a zero-day vulnerability in a service on one of Product A's nodes let the attacker run a hidden script under the service process, read the environment variable holding the database password and connect to the database, and the same hidden-script activity appeared on two more nodes on 2026-09-23 and 2026-09-25 (UTC+8). Early on 2026-09-25 (UTC+8) the attacker entered Product B's management platform under an internal employee's identity, made three attempts to inject system commands into task parameters to write malicious files, and then submitted code through the platform's web execution endpoint, attempting to modify server configuration, write a communication relay file and upload and assemble malicious program files in batches. SlowMist also recovered, from files the attacker had deleted, a withdrawal tool built for Bitget's withdrawal logic that forged risk-control parameters and invoked the withdrawal process, and records that the attacker later tried to alter withdrawal records directly in the wallet database (SlowMist, 2026-09-29). Neither report names the appliance vendors.

For defenders, the appliance class is security and network appliances with privileged reach into a production backend, and the observable behaviour is a web shell or hidden script running under the appliance's own service process, a new outbound command-and-control connection from the appliance, and sessions from the appliance to production servers (Mandiant, 2026-09-28) (SlowMist, 2026-09-29).

Builds on: SentinelLabs: the same DPRK backdoors from a $292M crypto theft resurface on a victim with no…

incident29 Sep 05:15Zmulti-sourceOpen finding →

2026-09-08 · view entry permalink →

NOTABLENATOB2

Sekoia and Kudelski Security split the 'Lazarus umbrella' into six named DPRK clusters, and document two of them adopting commodity ransomware-as-a-service within two months of each other

Sekoia's TDR team and Kudelski Security, a Switzerland-based research firm, jointly published a reassessment of how North Korea's offensive-cyber apparatus is organized (Kudelski Security, 2026-09-07). The authors now track the historical "Lazarus umbrella" as six distinct sub-clusters (TEMP.Hermit, Citrine Sleet, CryptoCore, Jade Sleet, Moonstone Sleet, and Famous Chollima, the last already tracked here as an alias of the North Korean fraudulent-IT-worker cluster) each carrying a different primary mandate spanning strategic espionage, dual espionage-and-revenue operations, and pure financially motivated crime (Kudelski Security, 2026-09-07). The espionage-focused clusters under GRIB (formerly RGB), TEMP.Hermit among them, are the authors' own described inheritors of both the historical Lazarus umbrella and the Kimsuky cluster's lineage, even where their precise bureau affiliation is debated within the CTI community (Kudelski Security, 2026-09-07). The authors date the Lazarus umbrella's internal reorganization into specialized sub-clusters to a 2018–2023 transition phase alongside the global expansion of the cryptocurrency market, out of which APT38 itself emerged as the financially-motivated sub-cluster; APT38 has since, per the authors' own current research, further split into two of these (CryptoCore and Jade Sleet) both exclusively financially motivated and focused on cryptocurrency, Web3 and blockchain targets, though the authors do not date this more recent split.

The most defender-relevant finding is a documented pattern of commodity-ransomware adoption by nominally espionage-focused units: Andariel, a dual-mandate cluster, used its own custom ransomware (Maui, H0lyGh0st) and separately collaborated with the criminal Play ransomware-as-a-service operation in 2024, citing prior reporting from Unit 42; Moonstone Sleet deployed its own custom malware (FakePenny) the same year and then adopted the Qilin ransomware-as-a-service in 2025, within two months of Andariel's own RaaS adoption (Kudelski Security, 2026-09-07). The authors note it is "interesting" that the two clusters integrated RaaS into their campaigns within two months of each other, a single observed timing overlap, not a claimed broader trend, though it is consistent with the general possibility that DPRK clusters rent commodity ransomware infrastructure alongside, or instead of, running only bespoke tooling.

The report also states that "Reaper" (already tracked here as an alias of ScarCruft/APT37) is the cluster aligned with North Korea's newly renamed National Intelligence Agency (formerly the Ministry of State Security, renamed June 2026), tasked with surveillance of defectors and South Korean NGOs and activists. Kudelski Security's own separate prior research, cited in this report, found that DPRK fake-IT-worker infrastructure and offensive-APT infrastructure share the same VPN exit nodes, a concrete pivot point for correlating IT-worker-fraud indicators against APT intrusion infrastructure (Kudelski Security, 2026-09-07). Separately, the report documents a Cambodia-based money-laundering hub, the Huione Group (flagged by the US Treasury's FinCEN as a primary money-laundering concern) whose executives the authors say have shown indications of direct ties to North Korean actors, with an estimated USD 37.6 million in DPRK-linked cryptocurrency laundered through it between 2021 and 2025 via stablecoins and technical tooling that let North Korea convert illicit proceeds into ostensibly legitimate assets (Kudelski Security, 2026-09-07).

We notably made our clustering evolved by splitting the Lazarus umbrella into six distinct sub-clusters: TEMP.Hermit, Citrine Sleet, CryptoCore, Jade Sleet, Moonstone Sleet, and Famous Chollima.

Sekoia TDR team / Kudelski Security

Of note, Andariel is particular as it used custom ransomware (Maui and H0lyGh0st) for financial theft, as well as ransomware-as-a-service (RaaS) developed by an operator of the Russian cybercrime ecosystem. It was notably observed collaborating with Play in 2024. Another DPRK cluster, Moonstone Sleet, acted similarly by deploying its custom malware FakePenny in 2024, but also the Qilin RaaS in 2025. It is interesting to note that the two clusters integrated RaaS in their campaigns within two months of each other.

Kudelski Security observed that fake IT workers and offensive teams often share the same VPN exit nodes.

Kudelski Security

Builds on: A Swiss research lab traces a stealer-log leak into DPRK gambling infrastructure and the… · The command-and-control channel is a legitimate cloud storage API, not a registered domain · Rapid7 finds a DPRK-nexus implant that falsifies HAProxy's own traffic counters so its…

research08 Sep 04:41Zsingle-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

  • Threats2
  • Research1

Source distribution

  • bitget.com2 (18%)
  • thehackernews.com2 (18%)
  • img.bgstatic.com1 (9%)
  • kudelskisecurity.com1 (9%)
  • raw.githubusercontent.com1 (9%)
  • sekoia.com1 (9%)
  • sentinelone.com1 (9%)
  • trmlabs.com1 (9%)
  • other1 (9%)
All cited sources (11)