Morning Threat Brief: FBI names North Korea in the $6.3 billion Binance theft, Chainalysis breached by agentic AI, and Northflank customers told to rotate everything

Good morning. The FBI has named the actor behind the largest crypto theft on record, and it published the wallet addresses to block. The firm that traces stolen crypto was itself breached by what it calls offensive agentic techniques, and a cloud platform told every customer to assume their secrets were decrypted. Block the wallets, rotate the secrets, and patch the container host.

1. FBI names North Korea in the $6.3 billion Binance theft: block the published wallets (TraderTraitor). The FBI said on October 31 that North Korea was responsible for the theft of more than $6 billion in virtual assets from Binance on or about October 29, tracking the activity as TraderTraitor, the same name it used for the $1.5 billion Bybit theft in February 2025. The bureau, with the Secret Service and IRS Criminal Investigation, says it has observed the actors converting stolen assets primarily into Ethereum and expects further laundering through DeFi platforms and instant swap services. It published hundreds of Ethereum addresses and 19 Bitcoin addresses holding or having held stolen assets, and urged exchanges, DeFi services, THORNode and RPC operators, analytics firms, and other virtual asset providers to block transactions with or derived from those addresses. Binance resumed withdrawals in phases on November 1 and says it has covered about 95 percent of the stolen tokens with company funds, with about $3 billion frozen through industry cooperation. One caveat: President Trump said Saturday the US was not yet certain North Korea was involved, so treat the attribution as the FBI's assessment, not a settled fact. If you run anything that touches crypto flows, ingest the FBI address list and screen for derived transactions, not just the listed wallets.

2. Chainalysis breached by what it calls offensive agentic techniques: customer names and emails exposed. The blockchain analytics firm, whose tools law enforcement and exchanges use to trace stolen funds, disclosed on October 30 to 31 that an external actor using offensive agentic techniques reached its internal systems and tools earlier in October. The accessed data covers customer user IDs, full names, email addresses, and organizational role labels. Chainalysis says it has found no evidence that investigation content, authentication credentials, or session tokens were touched, and says the incident is unrelated to the Binance theft. What it has not said: which flaw was exploited, how long the actor was inside, or which internal tools were reached. If you are a Chainalysis customer, treat the exposed names, emails, and role labels as phishing fuel: warn staff, and verify any message claiming to be from Chainalysis through another channel before acting on it.

3. Northflank breach: assume every stored secret was decrypted and rotate it all. The cloud platform for apps and AI services told customers to assume their environment variables were decrypted after a breach led to abuse of customer AI API keys, with customers reporting unauthorized key use running up provider charges. Wiz, which alerted Northflank on October 30, counts nine AI developer platform incidents in October alone, including OpenCode, Railway, Warp, Lightning AI, and Northflank, with attackers hunting stored AI credentials for LLMJacking and resale. Northflank has enabled credential rotation and audit logs but has not disclosed how attackers got in. Rotate every secret stored on the platform, audit AI spend and access logs for charges you did not make, and reissue keys rather than reusing anything that lived there.

4. LXD and MicroCloud carry a 10.0 flaw that lets an attacker impersonate a trusted client (CVE-2026-112816). Canonical fixed a maximum severity flaw in LXD and MicroCloud that lets an attacker who can reach the HTTPS API over the network, and who holds a trusted client's public certificate, log in as that client without the private key. Affected versions are LXD 4.0.14, 5.0.10, 5.21.8, and 6.9 before their fixed releases. The bug was reported by the Incus project, which began as a community fork of LXD, and Canonical confirmed it affected LXD as well. There is no public sign the flaw has been used in an attack, it is not on CISA KEV, and no working exploit has been published. Upgrade LXD and MicroCloud to the fixed releases, restrict who can reach the API over the network, and audit your trusted client certificates while you are there.

Warning: two federal KEV deadlines land today, Sunday, November 1: GitLab CVE-2026-97229 and Cisco CVE-2026-76418. The Ivanti privilege escalation flaw CVE-2026-111357 is due tomorrow, Monday, November 2. Patch before the weekend ends, not on Monday morning.

Full writeups: kevinthecyberguy.com/vuln-watch
Indicators to hunt: kevinthecyberguy.com/ioc-library

New CISA KEV additions today: none. The catalog stands at 1,766 entries, last updated October 30.

← kevintswaney.com