← All briefs
high May 28, 2026

Seedworm Espionage Campaign Against Electronics Manufacturers: Credential Theft, DLL Sideloading, and Covert Exfiltration

Source report →

Seedworm, an Iran-aligned threat actor tracked under aliases including MERCURY, MuddyWater, Temp Zagros, and Static Kitten, has been observed conducting a broad espionage campaign that reached 9 organizations across 9 countries in Q1 2026 alone. Confirmed victims include government agencies and an international airport in the Middle East, electronics and industrial manufacturers in Southeast Asia and South Korea, a financial services provider in Latin America, and education, public-sector, and professional services organizations across multiple regions. First detected in February 2026, the intrusion chain reflects a notable tradecraft evolution toward quieter, more disciplined operations, with Node.js orchestration replacing raw PowerShell to keep activity away from script-block logging, and multiple credential-theft tools deployed so that blocking any single binary does not halt the operation.

Initial execution is orchestrated through Node.js scripts that invoke PowerShell for download cradles and secondary payloads fetched from a hard-coded staging IP and a secondary attacker-owned domain, giving the operator two independent fetch channels. The group stages malicious DLLs alongside legitimate, signed binaries from vendors such as Fortemedia and SentinelOne, exploiting DLL search-order loading to execute implants under the cover of trusted software. Persistence is established via a Run registry key pointing to the sideloaded payload, and a dedicated proxy tool provides a covert relay channel back to attacker-controlled infrastructure.

Seedworm conducts systematic reconnaissance prior to lateral movement: operators run whoami, ipconfig, net commands, and WMI queries against the SecurityCenter2 namespace to enumerate users, domain groups, and installed security products. Credential material harvested from SAM, SECURITY, and SYSTEM registry hives as well as browser profile stores is staged in the Windows Temp directory and exfiltrated using curl with multipart form upload to the public file-sharing service sendit.sh. The use of anonymous file-transfer infrastructure and legitimate signed binaries reflects a deliberate effort to blend into normal endpoint activity.

IP ADDRESS 3
179.43.177.220
178.128.233.36
37.187.78.41
DOMAIN 2
timetrakr.cloud
svc.wompworthy.com
SHA256 FILE HASH 7
d587959841a763669279ad831b8f0379f6a7b037dffc19deab5d41f37f8b5ffc
74ab3838ebed7054b2254bf7d334c80c8b2cfec4a97d1706723f8ea55f11061f
c6182fd01b14d84723e3c9d11bc0e16b34de6607ccb8334fc9bb97c1b44f0cde
0c9b911935a3705b0ad569446804d80026feb6db3884aeb240b6c76e9b8cf139
3ee7dab4ae4f6d4f16dfabb6f38faef370411a9fc00ff035844e54703b99600a
bee79c3302b1a7afc0952842d14eff83a604ef00bfdae525176c16c80b2045f7
b21c802775df0c0d82c8cfde299084abc624898b10258db641b820172a0ba29a
URL 4
http://179.43.177.220:8080/nm.ps1
http://179.43.177.220:8080/a.dat
http://179.43.177.220:8080/a.exe
https://timetrakr.cloud/sp.ps1

Detections (9)

Enable detections →

Connect your environment for suggestions and queries personalized to your security telemetry.

  • Security Vendor Binary Spawned by Node.js
  • Process Connection to Chrome App-Bound Encryption Tool Repository
  • PowerShell Reconnaissance Spawned by Node.js
  • Security Product Discovery Via WMI SecurityCenter Namespace
  • Potential Persistence Attempt Via Run Keys Using Reg.EXE
  • Credential Dialog Spoofing via CredUIPromptForWindowsCredentialsW
  • Remote Thread Creation Targeting a Browser Process
  • Non-Browser Process Opening Browser Credential Database Files