TRASCRIZIONE 🔗
WEBVTT
00:00:10.320 --> 00:00:14.160
Here is your briefing for Wednesday, November 11th, 2026.
00:00:15.280 --> 00:00:24.640
Attackers are already using an Outlook bug where one opened email file can hand over your Windows login hash, and it's shipped in a patch Tuesday with more than 1200 other fixes.
00:00:27.839 --> 00:00:30.880
One click in Outlook can hand over your password hash.
00:00:31.120 --> 00:00:36.320
Microsoft's November Patch Tuesday fixes 1259 flaws.
00:00:36.560 --> 00:00:40.960
The second month in a row, over a thousand, but only one is confirmed under attack.
00:00:41.039 --> 00:00:42.799
It's a spoofing bug in Outlook.
00:00:42.879 --> 00:00:51.439
Open a crafted message file, and Outlook quietly connects to an attacker's server without the usual external content warning, leaking your Windows login hash.
00:00:52.239 --> 00:00:54.000
Microsoft rates it moderate.
00:00:54.239 --> 00:00:57.039
Researchers at Action 1 say that label undersells it.
00:00:57.199 --> 00:01:01.519
Since a captured hash can let an attacker sign in as you and move to other systems.
00:01:01.759 --> 00:01:07.359
Anthropics researcher found it with help from Claude and CISA gave federal agencies until November 24th.
00:01:07.519 --> 00:01:13.600
Also in the pile, remote code, execution bugs in Windows Search, Directory Services, and the Windows Encryption Library.
00:01:13.760 --> 00:01:14.480
Do this today.
00:01:14.640 --> 00:01:24.880
Push this month's Office and Microsoft 365 apps, update, and block outbound Windows file sharing traffic on port 445 at your firewall, so leaked hashes have nowhere to go.
00:01:28.160 --> 00:01:31.040
XN Orchestra will let anyone in with an empty cookie.
00:01:31.200 --> 00:01:37.600
VATES, the French company behind it, warns that attackers are actively exploiting a critical authentication bypass.
00:01:37.760 --> 00:01:47.600
Send a login cookie containing an empty object, and the token lookup treats it as give me the first token, which logs the attacker in as that token's owner, usually an admin.
00:01:48.640 --> 00:01:54.480
From there, it's code execution on manage pools and a full takeover of the virtualization host as root baits.
00:01:54.800 --> 00:02:06.160
Tie the activity to an address flagged as a redline steeler control server, and list Telltale signs, a virtual machine named Pivot2, OddSerial Console settings, and cron files with Oostar in the name.
00:02:06.320 --> 00:02:07.520
There's no CVE yet.
00:02:07.680 --> 00:02:08.400
Do this today.
00:02:08.560 --> 00:02:11.599
Update Zine Orchestra to this week's stable or latest release.
00:02:11.759 --> 00:02:17.120
Pull it off the internet and hunt your logs for requests carrying an empty authentication token.
00:02:20.640 --> 00:02:24.480
Stolen AI keys just ran up a$740,000 tab.
00:02:24.640 --> 00:02:34.560
The app hosting platform Railway says in October breach, let an attacker decrypt stored environment variables in up to about 100,000 workspaces, specifically hunting for AI provider keys.
00:02:34.719 --> 00:02:41.520
Those keys were then used for an estimated$740,000 in unauthorized usage, likely resold for model distillation.
00:02:42.560 --> 00:02:55.439
The attacker escaped a build sandbox, grabbed a build credential that internal systems trusted far too much, copied Railway's own code, found a misconfigured cloud identity binding, and walked to a machine that could decrypt customer secrets.
00:02:55.599 --> 00:03:01.039
After first saying it couldn't refund anyone, Railway now says it will cover charges the AI providers won't.
00:03:01.280 --> 00:03:06.319
Wiz counts at least nine AI developer platforms breached in October, all chasing the same thing.
00:03:06.560 --> 00:03:16.879
Do this today if you host on Railway, revoke and reissue every key stored there before October 21st at the provider that issued it, and set hard spending caps on every AI provider account you own.
00:03:20.480 --> 00:03:23.680
Cloning the wrong Git repo can now run someone else's code.
00:03:23.840 --> 00:03:32.000
The Git project fixed a flaw where an extremely long file path slips past a safety check, then gets cut down on disk to a name the attacker picks.
00:03:32.159 --> 00:03:39.759
That lets a malicious repository swap a submodule's Git file for a link to a folder full of hostile hooks, which run during a recursive clone.
00:03:40.800 --> 00:03:46.960
Five other bugs got fixed too, including one that lets anyone who can open a pull request corrupt memory on the code hosting server.
00:03:47.200 --> 00:03:52.560
GitHub has already patched its cloud service, but Git for Windows hadn't shipped a fixed build as of Tuesday evening.
00:03:52.800 --> 00:03:53.680
Do this today.
00:03:53.840 --> 00:03:57.520
Update Git on every laptop and build runner to this week's release for your series.
00:03:57.680 --> 00:04:02.719
Patch GitHub Enterprise Server and stop recursively cloning repositories you don't trust.
00:04:06.080 --> 00:04:08.719
Grok Build's private share links weren't very private.
00:04:08.879 --> 00:04:19.279
Researchers at Claroc found more than 43,000 app links on the Grok.me domain through public domain lookup records, and about 35,000 open straight into the app and its data.
00:04:19.439 --> 00:04:25.759
The random words that were supposed to hide each link sit in the domain name, which every lookup server logs, instead of in the path.
00:04:26.800 --> 00:04:39.439
Exposed data included worker medical exams, employee rosters, a Navy contractor staff list, sales pipelines, and two dozen internal apps from SpaceX SI itself, which pulled those after Rs asked questions.
00:04:39.600 --> 00:04:45.759
Clorox says sharing defaulted to anyone with the link, and that Lovable Bolt and Replit apps get exposed the same way.
00:04:45.920 --> 00:04:46.639
Do this today.
00:04:46.800 --> 00:04:56.560
Open every Groc build or similar vibe-coded app you've shared, switch it to invited users or only you, and assume anything sensitive behind a public link has already been seen.
00:04:59.759 --> 00:05:10.000
An email file that leaks your login, an empty cookie that grants admin, keys left in a hosting vault, a repo that runs code on clone, and share links broadcast through public lookup records.
00:05:10.160 --> 00:05:13.280
Every one of them is a secret that was easier to reach than anyone assumed.
00:05:16.983 --> 00:05:20.742
That's your brief, stay sharp, patch your systems, and we'll see you tomorrow.