Trapdex Subscribe

CampaignsFake interview / recruiter lure

TraderTraitor Terraform 'candidate repos' dropping FLATROOF and ROOFDECK

Am I affected?

  • A .terraform.lock.hcl you ran names a hashicorp-aws or hashicorp-terraform host
  • You cloned exubient0/terraform-candidate-repo or chainstacker/Northwind-IAC

Do this now

  1. Reject lock files referencing hosts other than registry.terraform.io
  2. Never run terraform init on candidate repos from credentialed workstations
  3. Block the typosquat registry domains

What happened

In Sep 2026, DevOps candidates got Terraform interview repos that fetched Rust backdoors from typosquatted HashiCorp domains.

Affects: DevOps and cloud engineers running take-home Terraform projects on machines with cloud credentials

  • Terraform
  • GitHub
  • macOS

Attack chain

  1. Lure

    Fake job interview with a DevOps/Terraform take-home project

    First seen

  2. Artifact

    .terraform.lock.hcl pointing to a malicious provider registry; trojanized terraform-provider binary

  3. Actor

    TraderTraitor / UNC4899 / Jade Sleet (attribution: SentinelLABS; basis: tooling and infrastructure overlap with earlier TraderTraitor operations)

  4. Infrastructure

    • Typosquatted Terraform registry domains
    • Dynamic-DNS C2

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
domainregistry[.]hashicorp-aws[.]com
domainregistry[.]hashicorp-terraform[.]io
domaintechnicais[.]sytes[.]net
ip176[.]97[.]114[.]232
repositorygithub[.]com/exubient0/terraform-candidate-repo
sha2563c254614de8c1a2f213c526b0e5072d43ffeb7cc340d9a4a6ebaa16592b3bbe0
repositorygithub[.]com/chainstacker/Northwind-IAC
domaindiagnose[.]hashicorp-terraform[.]io
domainsupportaru[.]serveftp[.]com
domainarusupport-region1-webhook[.]online
domainstage-fashion365[.]vercel[.]app
domaindelay[.]servehttp[.]com
sha256188bd4fc222c9615540884920caf37ea88bcbea7488e1fb98709e357dd096666

Defender actions

  1. Allowlist Terraform provider sources and reject lock files that reference hosts other than registry.terraform.io
  2. Never run terraform init on external or candidate repos from workstations that hold cloud credentials
  3. Block the typosquat registry domains

Summary

DevOps candidates received interview projects whose .terraform.lock.hcl pointed a custom provider at typosquatted HashiCorp registry domains. Running terraform init fetched ARM64 Rust backdoors: FLATROOF for data theft and ROOFDECK for reconnaissance and lateral movement. SentinelOne documented a victim at an IT-services firm with no crypto ties.

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • The SentinelLABS page rate-limited our fetches; its content was confirmed through a syndicated copy and THN.
  • The repo and FLATROOF hash come from ReversingLabs. The RL source date is approximate.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.