The Stack — November 04, 2026

Daily IT Briefing: Nov 4, 2026

Today's theme is the trust you didn't know you were extending: to a firmware spec, a settings toggle, a hosting provider's backups, or a "test assignment" from a recruiter. Binance's timeline shows how one detected intrusion still gave attackers enough to come back.

---

Cybersecurity Binance publishes a preliminary timeline of the ~$6.34B breach

Follow-up. The theft, FBI attribution, and Binance's reimbursement from reserves were covered Nov 1–2. This item covers only the new detail.

Binance's preliminary findings describe a four-month campaign, not a single laptop compromise:

| Date | What happened (per Binance) |

|---|---|

| June 2026 | An engineer installed a fake Homebrew package while trying to set up a "popular AI coding tool." Security detected an anomaly, replaced the device and rotated credentials. By then, attackers had already mapped the engineer's role and colleagues. |

| September 2026 | A second developer went through two fake job interviews. He then ran a malware-laden "test assignment" on his work machine, and the attackers covered their tracks. |

| Oct 20 | Using that machine and Binance's own internal AI tool, attackers pulled data on two employees, one of whom held the privileges they needed. |

| Oct 29 (evening) | Attackers connected to the device, used stolen credentials and ran a malicious script to execute the theft. |

Other new points

• Binance says it blocked 57 threats it attributes to North Korea during 2026.
• Pyongyang called the FBI attribution "absurd rhetoric."
• Binance says its own findings still need independent verification. The loss figure and the claim that user funds are safe both remain company statements.

Technical takeaways

• Remediation is not the same as containment. The June incident was caught and cleaned up, but the reconnaissance had already succeeded. Incident response should assume that org-chart and role information has leaked, not just credentials.
• AI tooling cuts both ways.
• Fake AI-coding-tool installers are a newer lure.
• Attackers abused an internal AI assistant to gather data on employees.
• Internal LLM tools that can query HR or directory data need the same access scoping and logging as any other privileged system.
• Developer workstations remain the soft target. Fake interviews, trojanized package managers and "take-home tests" are all well-documented tactics of DPRK-linked groups. Policies against running untrusted code on work machines need enforcement, not just documentation.

---

"BlackX" UEFI bootkit infects fully patched Windows machines

A UEFI bootkit dubbed BlackX is reportedly infecting Windows PCs that were fully updated.

How it works. It exploits ambiguity in how Microsoft documents and enforces Secure Boot. This is a gap in specification and enforcement, not a missing patch.

Why it matters. Bootkits run before the OS loads. That means they:

• evade most endpoint tooling
• can survive OS reinstalls and, depending on where they persist, disk replacement

Who is responsible is contested. Coverage questions whether Microsoft's unclear Secure Boot guidance created the gap. It is not settled how much responsibility falls on Microsoft, on OEMs' firmware and key configurations, or on administrators.

What to do now

• Verify that Secure Boot is actually enforced, not just enabled.
• Check whether the latest DBX revocation updates are applied.
• Watch for OEM firmware advisories.
• For high-value machines, consider firmware integrity measurement, such as TPM-based measured boot with remote attestation.

---

Beget's recovery update: cloud customer data is gone

Follow-up on the Russian hosting provider's outage after a cyberattack.

Beget's interim update is bleak:

• Lost entirely: all data in its VPS, S3-compatible object storage and managed Kubernetes services.
• VPS backups: image-level backups were destroyed. File-level backups survived, so some data can be partially recovered.
• Network configuration: CDN configs and IP settings were also lost. The company says it is still looking for ways to restore them.
• Timeline: the company says recovery "will take significant time."
• Unknowns: there is still no word on attribution or the initial access vector.

The lesson. Backups that share infrastructure, credentials or a control plane with production are not really backups. If your only copy lives with your provider, a provider-level compromise is a total-loss scenario. Keep offsite, separately credentialed and ideally immutable copies.

---

AI & ML Reports that OpenAI's "Improve the model" setting turned itself back on

A developer reports that the "Improve the model for everyone" toggle was re-enabled without consent on several coworkers' accounts. Their company had deliberately disabled training on Codex chats to protect proprietary code. The post links to an earlier report of similar behavior.

Caveats

• These are anecdotal user reports.
• OpenAI has not confirmed a bug or a policy change.
• Possible explanations include a settings-sync bug, an intentional reset, or confusion between account-level and workspace-level controls.

What to do if you handle proprietary code

• Audit the toggle at `chatgpt.com/settings/data-controls`.
• Consider filing a formal opt-out via `privacy.openai.com`.
• For teams, Business/Enterprise tiers, which exclude training by default under contract, are more reliable than per-user toggles.

---

Google ties schools' Search access to its AI features

According to reporting and a Google education blog post on its 2026 "AI learning era" updates, schools that block Google's AI features will also lose student access to Google Search.

What's unclear

• Which products and account types are affected (e.g., Workspace for Education).
• Timelines.
• Whether partial AI blocking is possible.

How it's being framed. Critics will likely see this as bundling and leverage. Google presents it as product integration. Check the policy text before forming firm conclusions. School IT admins should review their Workspace for Education controls now.

---

Anthropic adds rules against cloning existing games in Claude

Claude now carries guidance discouraging users from cloning existing games. The prevailing assessment is that this will barely dent AI-assisted copying, because plenty of other models and tools, including open-weight ones, will do the job. This is commentary, but it reflects a broader point: guardrails set by one vendor don't add up to industry-wide enforcement.

---

Unverified: "Astra" weight-editing results

Claims are circulating about an MIT CSAIL system called Astra. It reportedly improves a Qwen model's math performance by editing weights directly, using Python and feedback from practice runs. The reported jump is 7.9% → 48.1% on MATH-500 with a 50-forward-pass budget.

Why to be skeptical. The text appeared as placeholder content in a hobby front-end project, with no linked paper. The authors reportedly call the results preliminary. Treat the figures as unconfirmed until a paper appears.

---

Hardware Apple reportedly targeting a ~$1,000 tabletop home robot for 2027

Reports describe a tabletop robot with fairly narrow functions:

• FaceTime calls
• Smart-home control, such as lights

Caveats

• This is reporting, not an Apple announcement. Price, timing and features could all change.
• The reporting names John Ternus as Apple's CEO. Ternus has long been Apple's hardware engineering chief, so verify that title independently before repeating it.
• The concern that a $1,000 price tag doesn't fit such limited functionality is commentary, not a product verdict.

---

Dev World "Hacker Times"

A hobby project re-renders a popular tech link aggregator's front page in New York Times newspaper style, turning submissions into article layouts. It's a fun UI and typography experiment. It also illustrates how easily sample text can be mistaken for news, as with the Astra item above.