← Back to Blog

The Tuesday Briefing — Nov 3, 2026

6 min readAtypical Tech
Illustration for The Tuesday Briefing — Nov 3, 2026

The Big Picture

One poisoned update to a coding tool was live for about 11 hours, and up to 5,000 developers may have installed it. That is the story of the week: the software your team trusts, including its AI helpers, is now a favorite way in. Several of this week's stories come down to one question: who can reach your accounts, keys and tools, and could you shut them off fast?

This Week's Top 5

1. A Fake Update to a Popular AI Coding Tool Planted a Backdoor

What happened: Tampered versions (2.1.312 and 2.1.313) of the Claude Code extension were live for about 11 hours on Oct 29. Cursor estimates up to 5,000 people may have installed it. The bad code tried to add a hidden login key, open a secret connection back to the attacker and keep itself running. Reporting describes a break-in at the distribution channel, not a flaw in Claude Code itself.

Why it matters to your business: Removing the extension does not remove the backdoor. Any developer who installed it may have handed over access to your code and cloud accounts.

What to do: Ask your developers or IT provider whether anyone installed that extension on Oct 29. If so, have them hunt for a hidden login key named "svc-telemetry," then change passwords and keys from a clean computer. Details here.

2. A $6.3 Billion Theft Reportedly Began on One Engineer's Laptop

What happened: The crypto exchange Binance says a record theft of about $6.3 billion traced back to a compromised laptop belonging to a DevOps engineer (a person who builds and runs the company's systems). The FBI and Secret Service blame North Korea's "TraderTraitor" group. Binance has not confirmed that attribution, and the laptop detail comes from preliminary findings.

Why it matters to your business: The computer your IT person or developer uses often holds the keys to everything else. One infected laptop can be enough.

What to do: Ask your IT provider whether admin and developer laptops are kept separate from everyday browsing, and whether high-value actions like moving money or deploying software need a second person to approve.

3. Hackers Are Poisoning Projects So Opening Them Runs Their Code

What happened: Security firm JFrog found 42 GitHub projects (shared code folders) rigged with hidden files for AI coding tools like Claude Code, Cursor, Gemini and VS Code. Opening one of these projects in those tools can run the attacker's code. It goes after saved passwords and keys for GitHub, cloud services and AI accounts.

Why it matters to your business: A developer who simply opens a project from the internet could expose your company's keys. No download or click on a suspicious file is needed.

What to do: Ask your developers to open unfamiliar projects only on a throwaway computer or virtual machine, and to turn off any "auto-run" setting in their AI coding tools.

4. A Hosting Platform Breach Led to Stolen AI Keys Being Used

What happened: The hosting platform Northflank told customers to change all passwords and secrets after a breach led to unauthorized use of customers' AI account keys. On Nov 2 it said customers on its shared control system should rotate secrets, starting with AI provider keys. How the attackers got in has not been disclosed.

Why it matters to your business: A stolen AI key can run up a large bill or expose company data, and the thief does the spending on your account.

What to do: Log in to each AI service your team uses, check for usage you do not recognize, set a spending cap, and replace the key if you host anything on Northflank. Read the report.

5. Fake IT Support in Microsoft Teams Is Tricking Employees

What happened: Attackers posing as IT help staff are contacting employees through Microsoft Teams, email and phone. They talk people into starting a remote-control session (such as Quick Assist), then use weak spots in the company's certificate system to get privileged access. Cisco Talos reports the same help-desk impersonation pattern.

Why it matters to your business: The message looks like it comes from a coworker, and a password reset may not undo access the attacker already created.

What to do: Ask your administrator to block or limit Teams chats from outside your company, and tell staff that real IT will never start a remote session after an unexpected chat. More on the scam.

Quick Hits

  • A GitLab flaw rated 10 out of 10 for severity is being actively exploited, and over 1,000 GitLab servers were still unpatched. If you host GitLab yourself, ask your IT provider to update it.

  • Ivanti Connect Secure, a remote-access product, has flaws that attackers chained together to take full control. The US government's patch deadlines were Nov 2 and Nov 13. Ask your provider whether you use it and whether it is updated.

  • Siemens SIMATIC IoT2050 devices have a flaw rated 10 out of 10 that is being exploited. Siemens fixed it in version 4.3.4.1 and later.

  • Attacks on supermarket refrigeration controls hit stores in at least nine European countries. Danfoss reportedly found attacks on 17 or more Dutch businesses, mostly small butchers and grocers. Any equipment reachable from the internet should be hidden behind a secure connection.

  • Synology warned customers to update their network storage (NAS) devices right away because of ongoing C3RB3R ransomware attacks.

  • Microsoft will retire text-message and voice-call sign-in in February 2027, so start moving staff to passkeys now.

  • The UK is subsidizing the Cyber Essentials security certification to as little as 80 pounds for vulnerable small businesses. UK readers should check their eligibility.

  • A Claude Code update (2.1.317) fixes a bug where output from one session could land in another session's record. If your team uses it in shared or cloud setups, update.

One Thing to Do This Week

Make a one-page "key list" of every AI tool and service your business uses, and set a spending limit on each. This week's Northflank breach and the poisoned coding tools both aim at the same prize: saved passwords and AI keys. For each tool, write down who owns the account, where the key is stored and who can see it. Then log in to the billing page and look for charges you do not recognize. Turn on a monthly spending cap if the service offers one. Finally, find out how you would replace each key in a hurry. If you do not know, ask your IT provider to walk you through it. A key you can swap in 10 minutes is far less scary than one you cannot find.

Worth Reading

Related Posts