Trapdex Weekly #1: Binance says a fake job interview led to the $6.3B theft

Trapdex™ Weekly #1 · 16 Nov 2026

Trapdex

Status as of 15 Nov 2026. Public reporting only, so nothing in this issue is rated above Moderate. All indicators are defanged.


Today we’re launching Trapdex, the live record of attacks that trick developers and employees into running something malicious, traced from lure to artifact to actor to infrastructure. Know the trap before you install it. Every Monday: one deep dive, five short items and a defender checklist. Every claim dated and sourced, every indicator defanged, corrections public.


Deep dive: fake interview → swapped dev tool → wallet signing service (Binance)

Categories: Fake-interview lure · Pipeline · Campaign page

The finding (3 Nov). Binance says a fake job interview, run as a take-home coding assignment on a work Mac, led to the theft of about $6.3B on 29 Oct. Confidence: Moderate.

Lure. In September, a fake “Project Director” approached a Binance software engineer on a legitimate job platform. Two staged interview rounds followed, first with “HR” and then with a “CEO” on a chat app. The process ended in a take-home coding assignment, which the engineer ran on a work Mac.

Artifact. Binance says the assignment dropped a malicious pyenv_ into Homebrew’s pyenv directory, deleted the real pyenv, renamed its copy into place, re-pointed the symlink and used it to spawn a zsh shell. On 20 Oct, the attacker used an internal AI tool to reach two more engineers. On 29 Oct, the attacker used a container-deployment token taken from one of their laptops to reach the wallet signing service. Binance published paths and file sizes but no hashes. ReversingLabs could not match the implant in its own data.

Actor: TraderTraitor (also tracked as Jade Sleet, UNC4899 and Slow Pisces). The FBI and US Secret Service attributed the theft to this actor in statements on 31 Oct and 1 Nov. Elliptic’s on-chain analysis (about 12,000 wallets across 11 blockchains) is consistent with that. Attribution of the lure stage rests on Binance’s account plus tradecraft overlap.

Infrastructure. None has been disclosed for this intrusion. ReversingLabs describes a TraderTraitor-attributed toolkit from the same period that uses a trojanized Terraform provider, a safari_updater loader and the FLATROOF backdoor hidden in a font file. That toolkit has not been shown to be the Binance artifact. We list it as same-actor tradecraft only.

Confidence: Moderate. The actor rests on US government attribution. The lure → artifact link rests only on the victim’s own report, which included no hashes. As of 14 Nov, Binance has still published no hashes. We have not analyzed any artifact ourselves.

Indicators (defanged)

  • Binance (paths only): /opt/homebrew/Cellar/pyenv/2.8.0/libexec/pyenv_ and a modified /opt/homebrew/bin/pyenv symlink
  • Related TraderTraitor toolkit (not the Binance artifact):
    • Lookalike registries: registry[.]hashicorp-terraform[.]io, diagnose[.]hashicorp-terraform[.]io
    • Payload and C2: supportaru[.]serveftp[.]com, arusupport-region1-webhook[.]online
    • Trojanized Terraform provider SHA-256: 188bd4fc222c9615540884920caf37ea88bcbea7488e1fb98709e357dd096666
    • safari_updater loader SHA-256: 451b586ec9d3c997b319986a1177829653e8ae641c953c05ede6a38616f2da97
    • FLATROOF font container SHA-256: 62e988e9affcd000657bef4db47eb2e85c9a4cc42f4832780a02e19624e36e38

Why it matters. The lure targeted one person, but the blast radius was the deploy pipeline. Three trust boundaries failed in turn: a personal hiring conversation, a package manager on a work laptop, and a long-lived deploy token on an endpoint.

Sources: ReversingLabs, 31 Oct (updated 4 Nov) · The Record, 2 Nov · BleepingComputer, 3 Nov · CNBC, 3 Nov

Defender action: ban interview and test code on corporate devices, and alert on writes under Homebrew Cellar/ and bin/ that don’t come from brew itself.


Five short items

1. 29 Oct: a trojanized Claude Code update shipped through Cursor’s marketplace. IDE extension · pipeline · Confidence: Moderate
From about 09:27 to 20:35 UTC on 29 Oct, Cursor’s marketplace served anthropic.claude-code 2.1.312 and 2.1.313 with a 66-line loader added before the legitimate extension code. The loader added the SSH key svc-telemetry, opened a reverse tunnel, set up persistence and beaconed to hxxp://134.209.82[.]225:8099/beacon. Cursor says at most about 5,000 users were exposed. It pulled the package, rebuilt the marketplace and pushed 2.1.314. The bad builds did not reach Microsoft’s Marketplace or Open VSX. Anthropic says “a malicious actor used access to Cursor’s marketplace.” On 13 Nov, Cursor said an attacker used an access key it had issued to Fireworks AI, which Fireworks exposed, to copy data from a shared storage bucket. Credentials found in that data then let the attacker place the malicious builds in Cursor’s marketplace cache. The actor is unattributed. Campaign page · OpenSourceMalware, 29 Oct · Implicator, 31 Oct · StepSecurity, 1 Nov · Cursor, 13 Nov
Defender action: find Cursor installs of 2.1.312 or 2.1.313, upgrade to 2.1.314 or later, search authorized_keys for svc-telemetry, and rotate every secret present on an exposed host.

2. 13 to 21 Oct: GhostAction’s October wave stalled, but the stolen access didn’t. Pipeline compromise · phishing lure · Confidence: Moderate
Between 13 and 21 Oct, about 1,800 hijacked GitHub accounts pushed some 72,000 commits into about 23,000 repos. The commits added workflows with harmless-sounding names such as audit.yml, code-review.yml and repo-health.yml, built to send CI secrets to 193.32.204[.]199:8080. GitGuardian reported on 27 Oct that it found no successful run of any workflow payload, because GitHub’s workflow hold stopped them. Two things still matter. First, about 1,400 of those accounts had already been used in the 8 Oct wave, so their tokens were never revoked. Second, a Node.js stealer disguised as fa-solid-400.woff2 was set to run from .vscode/tasks.json whenever a developer opened the repo, a path the workflow hold doesn’t cover. GitGuardian has no evidence that it ran. As of 14 Nov, no malicious npm or PyPI releases have been tied to the stolen tokens. The actor is unattributed. Campaign page · GitGuardian, 27 Oct · GitGuardian, 7 Oct (updated 13 Oct)
Defender action: revoke tokens and OAuth grants for any account that pushed unexpected workflows, even where the run was blocked, and review tasks.json entries with runOn: folderOpen.

3. 29 Oct: Socket ties 319 browser extensions, with about 13.4M users over a decade, to search hijacking. Browser extension · Confidence: Moderate
On 29 Oct, Socket tied 319 Chrome extensions, active between 2016 and 2026, to search-monetization infrastructure. Socket counts about 13.4M users across them over that decade. They posed as PDF converters, manual finders, safe-search utilities and “AI search” tools, and were often promoted through ads. No code is needed: a single manifest key (chrome_settings_overrides) swaps the default search engine, and queries pass through the operators’ servers before reaching Yahoo or Bing with referral tags. Most had been removed from the Chrome Web Store by the time Socket published, but removal from the store doesn’t uninstall them. New domains and lures keep appearing. Socket links about 200 of the extensions to named advertising companies through ad-transparency records, privacy policies and domain data, and lists the operators of the rest as unknown. We have not verified those attributions, so we don’t repeat the names here. Socket, 29 Oct · BleepingComputer, 29 Oct
Defender action: allowlist extensions through enterprise policy and flag any installed extension that uses chrome_settings_overrides.

4. 19 Oct: a malicious color picker turns into a release-asset swap at OVHcloud. Pipeline compromise · IDE extension · Confidence: Moderate
From 12:47 to 14:21 UTC on 19 Oct, an attacker used a contributor’s GitHub account to replace the binaries on ovhcloud-cli releases 0.11.0 to 0.15.0 with a credential stealer. They updated checksums.txt last, so the published hashes matched the malicious files. StepSecurity traces the access to color-picker-universal 2.8.91, a VS Code extension the developer had installed a year earlier, which left a Node.js backdoor talking to 162.33.177[.]177. About 250 downloads happened during the window. OVHcloud shipped a clean, immutable, attested 0.16.0 the same day. Actor: GlassWorm operators, according to StepSecurity, based on a Solana dead-drop C2, extension-based initial access and matching loader and geofence logic. Exfil: hxxps://45.32.148[.]174/upload. Stage-1 SHA-256: 43df42fd79f6f81e530892b54634598770d6e496796a863c596e616bcb3fec70. Campaign page · StepSecurity, 19 Oct · BleepingComputer, 20 Oct
Defender action: if ovhcloud-cli was downloaded on 19 Oct, upgrade to 0.16.0 and rotate the credentials on that host; verify releases with signatures or attestations, not a checksums file shipped next to the binaries.

5. 18 Sep (background): four governments name WaterPlum (“Contagious Interview”). Fake interview · Confidence: Moderate
This is a different North Korean cluster from the deep dive, but the playbook rhymes. An 18 Sep joint advisory from seven agencies in Japan, the US, Australia and Germany, including Japan’s NPA, the FBI, Australia’s ACSC and Germany’s BfV, says the group infected at least 30,000 devices between Dec 2025 and Jul 2026 and moved $10.7M in crypto. Its tools were fake recruiters on job and freelance boards, AI face-swapped video interviews, coding tests, trojanized VS Code tasks.json files and npm packages. The malware families named are BeaverTail, InvisibleFerret, OtterCookie, OtterCandy and StoatWaffle. The attribution rests on the joint government advisory. Campaign page · ACSC advisory, 18 Sep · FBI joint advisory (PDF), 18 Sep · BleepingComputer, 19 Sep
Defender action: verify recruiters out of band, and run any coding test in a disposable VM, never on a corporate device.


What’s on Trapdex

  • Campaign pages for the campaigns in this issue and 50 more, each with its full chain, confidence, defanged indicators and sources, plus dated corrections whenever we make one. → Campaigns
  • In focus: the most-hit attack type of the last 90 days, with its newest case and three standing defenses. At launch, that’s fake job interviews. → Home
  • Check your stack: pick the tools you use (VS Code, Cursor, npm, GitHub Actions, Chrome and more) and the campaigns that touch them light up. Saved in your browser only; nothing is sent. → Home
  • Live events feed: automated, labeled unverified, updated after each collector run. Filter by category, platform, source and date. → Live events
  • Indicator search runs in your browser. Nothing you type leaves the page. → Search
  • CSV and JSON downloads of campaigns and indicators, for your blocklists and hunts. → Downloads
  • Methodology, covering how we collect, what we publish and what we never publish. → Methodology

Defender checklist

  • ☐ No interview code on corporate devices. Tell engineering and recruiting staff this in writing, and give them a disposable VM.
  • ☐ Watch your toolchain binaries. Alert on writes under Homebrew Cellar/ and bin/ that don’t come from brew itself, especially pyenv, node and python.
  • ☐ Get deploy tokens off laptops. Use short-lived, workload-bound credentials. Alert on deployments that originate from developer endpoints.
  • ☐ Inventory Cursor installs for anthropic.claude-code 2.1.312 or 2.1.313. Search authorized_keys fleet-wide for svc-telemetry. Rotate every secret that was present on an exposed host.
  • ☐ Treat each fork marketplace as its own supply chain. Pin versions and turn off auto-update for high-privilege extensions.
  • ☐ Lock down .github/workflows/ with CODEOWNERS and alerting. Set the default GITHUB_TOKEN to read-only. Revoke tokens and OAuth grants for any account that pushed unexpected workflows, even if the run was blocked.
  • ☐ Keep VS Code Workspace Trust on. Review tasks.json entries with runOn: folderOpen, unexpected font files run by node, and any MCP server an extension declares.
  • ☐ Verify releases out of band. Check signatures or attestations, or pin hashes from a channel other than a checksums file shipped next to the binaries. Turn on GitHub immutable releases for your own projects.
  • ☐ Check browser search settings fleet-wide. Allowlist extensions through enterprise policy, and flag any extension using chrome_settings_overrides.
  • ☐ Pin your Terraform registry to registry.terraform.io, and block the lookalike registries above.

How we rate confidence and fix mistakes: Confidence scale and corrections policy. Named in an item and think we got something wrong? Tell us through our contact page. We answer every dispute and log the outcome.

Know someone who runs CI or hires engineers? Forward this. Got it forwarded? Subscribe to Trapdex Weekly. · Trapdex

Trapdex Weekly
editor@trapdex.com
Trapdex™
Trapdex · PO Box 16 · Cresskill, NJ 07626


Get Trapdex Weekly

Free every Monday at 08:00 ET. One email a week, unsubscribe anytime.