Team Cymru Details Telemetry Signals for Detecting DPRK Remote IT Workers

· Original article ↗

Summary

Team Cymru outlines telemetry signals for spotting DPRK operatives posing as remote IT contractors, including VPN and network patterns, remote-access tools, certificate fingerprints, and unusual outbound activity. It also cites an incident involving LND[.]fi.

Key points

  • The article says DPRK operatives pose as freelance developers or IT contractors to gain access to organizations, sometimes through staffing vendors and outsourced development firms.
  • Suggested telemetry signals include connections to Astrill VPN exit nodes, activity on specified Russian and Chinese networks, remote-access tools, and their X.509 certificate fingerprints.
  • Other signals include persistent outbound traffic during off-hours or from unusual geolocations; the article says these patterns are more telling in combination.
  • The article cites an FBI account of two DPRK nationals using false identities at 64 companies and generating up to $866,000, and a U.S. DOJ account linking a broader IT-worker network to over $6.8 million in revenue between 2020 and 2023.
  • The article reports that a contractor hired by LND[.]fi later used administrative access to steal $1.27 million; it presents this as an example of the risk from inadequate identity verification.
  • It recommends monitoring outbound connections, correlating remote-access activity with IP metadata and TLS certificates, and investigating behavioral anomalies among employees and third-party vendors.

Article Details

Defense Focus
Use internet telemetry to identify DPRK-linked remote workers by correlating network infrastructure, remote-access activity, and behavioral anomalies.
Detection Methods
  • Look for connections to known VPN exit nodes, including Astrill VPN.
  • Correlate repeated activity from Russian or Chinese networks with other indicators.
  • Cross-reference remote-access activity with IP metadata and X.509 certificate fingerprints.
  • Investigate persistent outbound traffic during off-hours or from abnormal geolocations.
  • Check for cloned developer infrastructure, such as identical GitHub templates.
  • Review whether third-party vendors communicate with flagged VPNs or DPRK-linked infrastructure.
Data Sources
  • Internet telemetry, including S2 NetFlow
  • Outbound connection and traffic patterns
  • IP metadata and geolocation
  • ASN information
  • X.509 certificate fingerprints
  • Remote-access activity
Defensive Actions
  • Monitor outbound connections to known DPRK-linked ASNs and flagged VPN infrastructure.
  • Correlate remote-access activity with IP metadata and TLS certificate fingerprints.
  • Apply the same infrastructure checks to third-party vendors.
  • Set thresholds for escalating behavioral anomalies for investigation.

MITRE ATT&CK

Vendors

Products

Countries

Industries

Related Articles