TraderTraitor’s Tradecraft: North Korean Crypto Theft Through Social Engineering and Supply-Chain Attacks

· Original article ↗

Summary

Wiz examines TraderTraitor, a North Korean-linked cluster attributed to major crypto thefts, and details its use of social engineering, trojanized software, supply-chain compromises and cloud access to steal digital assets.

Key points

  • The article describes TraderTraitor as financially motivated North Korean activity linked by authorities and researchers to Lazarus and associated groups.
  • Earlier campaigns used fake job offers and trojanized cryptocurrency applications to deliver malware such as MANUSCRYPT, which could collect system information and execute commands.
  • In 2023, operators used malicious npm packages and GitHub collaborations to target developers; GitHub suspended accounts and repositories associated with the campaign.
  • In the JumpCloud compromise, attackers abused the provider’s privileged access to push a malicious update to fewer than five cryptocurrency-industry customers, according to JumpCloud.
  • In the DMM Bitcoin theft, authorities attributed the diversion of 4,502.9 BTC, valued at about $308 million, to TraderTraitor; the article describes stolen credentials and session cookies as part of the access path.
  • The article says the Bybit theft involved compromised developer access, stolen AWS session tokens, cloud reconnaissance and malicious JavaScript that altered transactions through Safe{Wallet}’s frontend; the FBI attributed the operation to TraderTraitor.
  • Wiz recommends limiting developer privileges, segmenting identities and networks, monitoring cloud credentials and configurations, and checking dependencies for suspicious packages.

Article Details

Attack Vectors
  • Phishing and social engineering using fake recruiter messages, job offers, coding challenges, and malicious links or attachments.
  • Trojanized cryptocurrency applications and malicious Python scripts used to execute malware on developer workstations.
  • Malicious JavaScript packages distributed through npm and other open-source supply-chain lures involving GitHub repositories.
  • Compromise of JumpCloud followed by abuse of its privileged access to push a malicious update to downstream customers.
  • Stolen session cookies and AWS session tokens used to access internal and cloud environments.
  • Malicious Docker image and cloud reconnaissance followed by JavaScript injection into Safe{Wallet}'s frontend to redirect cryptocurrency transactions.
Defensive Notes
  • Apply network and identity segmentation to limit lateral movement to privileged identities and sensitive resources.
  • Use least-privilege permissions for developers, especially in production and CI/CD environments.
  • Monitor cloud configurations and secrets, including AWS credentials and SSH keys, for anomalies or exposure.
  • Track code dependencies and investigate suspicious packages and the cloud resources they may affect.
  • Monitor for cloud asset enumeration, compromised cloud keys, suspicious MFA device registration, and connections to campaign-associated IP addresses.
  • Investigate malware matching campaign indicators in the environment.

Indicators of compromise

TypeIndicatorContext
DOMAINgetstockprice[.]comAttacker-registered domain used as a command-and-control endpoint in the Bybit operation.

MITRE ATT&CK

T1027 · Obfuscated Files or InformationThe second-stage payload delivered by the malicious applications was encrypted with AES-256.T1059.006 · PythonA Ginco developer was lured into running a malicious Python script from a fake coding challenge.T1059.007 · JavaScriptTraderTraitor applications used JavaScript and Node.js to execute malicious code.T1082 · System Information DiscoveryMANUSCRYPT collected system information from infected machines.T1105 · Ingress Tool TransferTraderTraitor applications retrieved encrypted second-stage payloads from hardcoded C2 URLs.T1195.001 · Compromise Software Dependencies and Development ToolsMalicious JavaScript packages from npm were introduced through GitHub-based developer collaboration lures.T1195.002 · Compromise Software Supply ChainThe JumpCloud compromise was used to push a malicious update to downstream cryptocurrency-industry customers.T1204.002 · Malicious FileVictims were lured into running trojanized cryptocurrency applications or malicious scripts.T1550.004 · Web Session CookieStolen session cookies were used to access Ginco's internal systems and pivot toward DMM Bitcoin.T1552.004 · Private KeysRN Stealer harvested SSH keys, saved credentials, and cloud configurations from files.T1553.002 · Code SigningSome malicious applications were signed with compromised or fraudulent Apple code-signing certificates to appear trustworthy.T1566.001 · Spearphishing AttachmentFake job-offer PDF attachments were used to deliver malware, including in the Ronin Network incident.T1566.003 · Spearphishing via ServiceTraderTraitor sent recruiter-themed phishing messages through services including LinkedIn, Slack, and Telegram.T1578.005 · Modify Cloud Compute ConfigurationsThe attacker tampered with Safe{Wallet}'s statically hosted frontend by injecting JavaScript that altered Bybit transactions.T1580 · Cloud Infrastructure DiscoveryDuring the Bybit operation, the attacker enumerated IAM roles, S3 buckets, and other cloud assets.

Threat Actors

Malware

Vendors

Products

Tools

Countries

Industries

Related Articles