Day Lila
Day Lila

Sunday, 25 October 2026

25 Oct · Cyber · In brief

Cyber · Sunday, 25 October 2026

Cyber, in brief

15 stories · 12 sources

Swipe up for the day in brief ↑Scroll down for the day in brief ↓

What is moving · 1 of 3

Stolen keys and logins

High ↑

LiteLLM's master key leaked in May and still worked in October. [1] Andromeda, which provides computing for AI work, says it found on 13 October that someone had reached credentials in its systems. [10] NordVPN, a security company, says it found 52 billion stolen browser cookies online in a year. [11]

What is moving · 2 of 3

Each copy needs its own fix

Building ↑

Bun, Python and Envoy each carry their own copy of Google's Brotli code and must each be updated. [6] Ruby fixed the bugs behind four GitLab flaws a month after GitLab first patched its own copy. [8][9]

What is moving · 3 of 3

Easier ways round strict checks

Building ↑

LiteLLM loosened its release approvals the same week it was attacked. [1] Fake Okta login pages steer YubiKey users to weaker text or email codes. [10] Chrome closed one easier path: it now asks before opening a page without encryption. [10]

LiteLLM says a key leaked on GitHub in May and never cancelled let an attacker take over its software releases

Swipe up for the story ↑Scroll down for the story ↓

LiteLLM, free software that connects company apps to AI services, said on Friday how its release was taken over: through a secret key that leaked in May and was never cancelled. [1]

it was posted on 27 May and used on 10 October [1]

Who is involved

Who is involved

Why it matters

LiteLLM is cancelling every token it holds, and the open question is whether the AI and cloud keys stolen from its own systems and its users' machines were used before they were changed. [1][3]

What's really going on

LiteLLM's attacker needed no new trick: a master key LiteLLM meant to cancel in May still worked in October, and a release rule loosened that same week let two stolen logins publish poisoned software. [1]

Who gains

An unlimited token taken with the old key gave owner-level access to every LiteLLM project on GitHub. [1]

Who pays

BleepingComputer says their machines should be rebuilt from clean backups and every key on them changed. [4]

Nobody knows yet

Whether the keys stolen from LiteLLM's systems and its users' machines were used.

Wiz saw stolen Amazon keys used about four and a half hours after the theft. [3] LiteLLM is still cancelling every token, and has not said what was done with the rest. [1]

Nobody knows yet

How the attacker found the May key.

LiteLLM says the file was overwritten quickly but has not said who saw it, or when, before that. [1]

Nobody knows yet

Which of LiteLLM's two accounts of the break-in is complete.

Its first account pointed to tokens leaking into its logs through Claude Code. [3] Its second traces the break-in to the May master key. [1]

Nobody knows yet

How many of the 49,000 downloads ran the poisoned code.

The figure is an estimate of downloads, not of machines where Python started with it installed. [3]

Good news

Security firms spotted LiteLLM's poisoned release within six minutes of it going online, and PyPI pulled it in under two hours.

The short version

That's the story in short.

The whole story has 12 more parts.

or swipe up for the next storyor scroll on for the next story ↓

The whole story, in 12 parts ↓

Part 1 of 12 · Who else is involved

Part 1 of 12 · Who else is involved

Part 2 of 12 · How it unfolded

Part 3 of 12

LiteLLM is downloaded about 92 million times a month from PyPI, the main store for Python software, and companies such as NVIDIA, Netflix and AT&T use it. [4]

Part 4 of 12

On 27 May a settings file posted to one of its public GitHub projects held the master key to an internal tool LiteLLM uses to run AI agents. [1]

Part 5 of 12

The team spotted the mistake quickly and wrote over the file, and listed the keys in it to be cancelled.

Part 5 of 12

The master key was never cancelled. [1]

Part 6 of 12

On 10 October an attacker used that key to get into the tool and took a GitHub login token stored there. [1]

Part 6 of 12

The token was not limited, and it belonged to the owner of LiteLLM's GitHub account, so it opened every project. [1]

Part 7 of 12

The same night the attacker ran hidden jobs that collected the GitHub logins of two engineers allowed to publish releases. [1]

Part 7 of 12

Socket, a security firm, found the jobs ran on branches made and deleted within minutes, leaving almost no trace. [1]

Part 8 of 12

Normally a release needs one engineer to start it and a special account, locked to a device in LiteLLM's office, to approve it. [1]

Part 8 of 12

That week the rule had been loosened so any two engineers could do both, to ship fixes faster. [1]

Part 9 of 12

The attacker used one stolen login to start the release and the other to approve it. [1][5]

Part 9 of 12

The poisoned version, 1.107.0, went out and was pulled on 21 October. [1]

Part 10 of 12

It was downloaded more than 49,000 times in about three hours, by one estimate. [3]

Part 10 of 12

Microsoft said on 23 October that deleting LiteLLM's own files can leave its hidden start-up code behind. [1]

Part 11 of 12

LiteLLM's first account, on 22 October, said the tokens had probably leaked into its own logs through Claude Code, an AI coding tool. [2][3]

Part 11 of 12

Friday's account traces the break-in to the May key instead. [1]

Part 12 of 12

LiteLLM says it is now cancelling every token for every internal system and outside service it uses. [1]

Brotli flaw reaches Bun, Python and Envoy

Swipe up for the story ↑Scroll down for the story ↓

A flaw in Brotli, Google's code for shrinking web data, also sits in Bun, Python's Brotli packages and the Envoy and Istio network tools. [6]

Bad compressed data can write past the end of a memory buffer, which can crash a program or let an attacker run code. [6]

Node.js and Google shipped fixes on 21 October. [7] Each program carries its own copy of the code, so each must be updated on its own. [6]

One flaw in Google's code, and a separate fix for every program that copied it.

CISA, the US cyber-defence agency, recorded no attacks on 23 October. [6]

Why it matters

In Python a program is exposed just by having the Brotli package installed, since common web tools unpack Brotli data by themselves. [6]

Why it matters

A running program keeps the old code until it is restarted. [6]

Who pays

Each program carries its own copy of Brotli, so each needs its own update and a restart. [6]

Nobody knows yet

Whether the Brotli flaw can take over real systems.

Imperva ran code on one unpatched Node.js build and has not released how. [6] Google rates the flaw 9.2 out of 10, Red Hat 8.1, and CISA recorded no attacks on 23 October. [6]

Good news

CISA's check on 23 October found no attacks using the Brotli flaw, two days after Node.js and Google shipped fixes.

Ruby fixes the bugs behind GitLab's flaws

Swipe up for the story ↑Scroll down for the story ↓

Ruby, a programming language, released versions 4.0.9, 3.4.12 and 3.3.13 on 23 October. [8] They fix three bugs in Onigmo, the part of Ruby that reads search patterns. [8]

Three bugs in Ruby's engine showed up first as four GitLab flaws. Every other Ruby program shares the engine.

Those bugs lay behind four critical flaws that GitLab, a site where teams store and build code, patched between 23 September and 21 October. [8]

The two October flaws needed no login and were rated 10 out of 10. [8] GitLab had fixed them by shipping its own patched copy of Ruby. [9]

Why it matters

Any program that turns text from an outsider into a search pattern was exposed, not just GitLab. [8]

Why it matters

Ruby 3.2 and older get no fix, and Ruby has not given the bugs their own ID numbers, so tools that check by number see only GitLab. [8]

Who pays

Ruby will not fix those versions, so the only cure is moving to a newer one. [8]

Nobody knows yet

How many other Ruby programs turn outsiders' text into search patterns.

Ruby has not given the bugs ID numbers of its own, so tools that check by number list only GitLab. [8]

Good news

Ruby fixed the three bugs behind four critical GitLab flaws, and none of the four was on the US list of flaws known to be used in attacks.

Phishing takes over 4,500 Bluesky accounts

Swipe up for the story ↑Scroll down for the story ↓

Bluesky, a social network, says a phishing attack has taken over more than 4,500 accounts. [10] Phishing tricks people into typing their login into a fake page.

The attack spread through posts promising a fake government payment. [10] Bluesky has suspended the taken accounts for now. [10]

It says it is working with their owners to secure the accounts and give them back. [10]

Why it matters

Owners whose accounts were suspended are told to email Bluesky's moderation team to get back in. [10]

Why it matters

Bluesky has not said who ran the attack or how many owners have their accounts back.

Who pays

Their accounts were taken over and are suspended until they contact Bluesky. [10]

Nobody knows yet

Who ran the Bluesky phishing, and how many owners are back in.

Bluesky has given a count of accounts taken over, but no attacker and no recovery figure. [10]

Fake Okta pages push users off hardware keys

Swipe up for the story ↑Scroll down for the story ↓

Dataminr, a firm that tracks threats, found phishing sites dressed as login pages for Okta and ServiceNow, two widely used business login and software services. [10]

They target companies that run the systems behind online shops. [10]

The pages ask people who sign in with a YubiKey, a small hardware login key, to switch to a code sent by text or email instead. [10]

Dataminr says this gets round the hardware key wherever company rules still allow those codes as a fallback. [10]

Why it matters

A hardware key only answers the real website, but a typed code can be passed on from a fake one.

Why it matters

Dataminr says breaking into these service firms gives attackers a way into the shops they serve. [10]

How it works

A strong check often keeps a weaker way round it, and attackers take that way

How it works

Companies keep an easier path beside a strict check, for lost devices or busy weeks, and attackers look for that path first.

How it works · step 1 of 5

A company sets a strict check, like an approval locked to one office device

How it works · step 2 of 5

It keeps an easier path beside it for lost devices or busy weeks

How it works · step 3 of 5

The easier path is used less, so fewer people watch it

How it works · step 4 of 5

An attacker who cannot pass the strict check looks for the easier path

How it works · step 5 of 5

The strict check never gets the chance to stop them

The twist

LiteLLM's approval account was locked to a device in its office, so nobody far away could steal it.

The twist

The attacker never needed it, because that week any two engineers could approve a release instead.

The picture

The attacker held two engineers' stolen logins. That met the looser rule, and the office device was never needed.

Seen the same day

Fake Okta pages and YubiKeys

The fake pages ask YubiKey users to switch to a text or email code, and that works only where the company still allows those codes as a fallback.

Seen the same day

52 billion stolen cookies

A website checks the password and second code once, then gives the browser a cookie so it need not ask again, and a thief with that cookie can often skip both checks.

Seen the same day

Chrome asks before unprotected pages

Chrome used to open unencrypted pages without asking unless a user had chosen its strongest safety mode, and now it asks every user first.

The catch

Some easier path is always needed, because people lose devices and urgent fixes must ship.

The catch

What decides the risk is whether anyone watches that path as closely as the strict one.

The whole

An engineer who wanted faster releases and a shopper who stays logged in each made a fair choice for their own week.

The whole

An attacker sees all those choices together, and each person sees only their own.

What's really going on

Elsewhere the same day, fake Okta pages steered YubiKey users to weaker text or email codes that their companies still allowed. [10]

Who gains

Wherever company rules still allow text or email codes, a fake Okta page can ask for one instead of the hardware key. [10]

ChatGPT's GitHub link can be turned on its owner

Swipe up for the story ↑Scroll down for the story ↓

Sunil Tripathy, a security researcher, showed a flaw in ChatGPT's link to GitHub, the site where programmers keep their code. [10]

Hidden instructions in a public project could lead ChatGPT, asked to review it, to write a job into a different, private project of the user. [10]

That job could then run and send the private project's secrets out. [10] Part of the cause is that the link's default setting reaches every project an account holds. [10]

OpenAI said the issue was out of scope for its bug reports. [10]

Why it matters

The attacker needs no access to the victim's account, only a public project and a request to review it, Tripathy says. [10]

Why it matters

Every user who left the default setting in place is inside its reach. [10]

Chinese coding AI writes weaker code for US clients

Swipe up for the story ↑Scroll down for the story ↓

Hirundo, an AI company, tested Qwen3-Coder, a Chinese AI model that writes software. [10]

It says apps were 19% more likely to be hackable when the model was told they were for a US defence contractor rather than a Chinese one. [10]

Apps for a Hong Kong democracy group were 28% more likely to let any user read everyone's secrets. [10]

Hirundo says the effect goes away when the model's pro-China leaning is removed. [10]

Why it matters

Companies around the world are building these open Chinese models into their work. [10] Booz Allen Hamilton, a US consulting firm, reported a similar finding in May. [10]

Nobody knows yet

Whether other Chinese coding models behave like Qwen3-Coder.

Hirundo tested one model, and Booz Allen Hamilton's similar finding in May came from its own tests. [10]

Laravel fixes a login skip

Swipe up for the story ↑Scroll down for the story ↓

Laravel, a popular toolkit for building websites in the PHP language, fixed a critical flaw rated 9.2 out of 10. [10]

It sits in TokenGuard, the part that checks the secret key an app sends to prove who it is. [10]

On some MySQL or MariaDB database setups, a specially shaped value could log an outsider in as another user without that user's key. [10]

The fix is in versions 13.29.0 and 12.68.0. [10]

Why it matters

Any page a site protects with that built-in check could have its accounts taken over by a stranger. [10] The attacker needs no login of their own. [10]

Three business tools fix serious flaws

Swipe up for the story ↑Scroll down for the story ↓

Three pieces of business software have fixes for flaws that let outsiders in, The Hacker News reports. [10]

GLPI, a tool firms use to track their computers and help-desk requests, had a flaw letting an outsider read its whole database, fixed in 11.0.9. [10]

Rapid7, a security firm, found three flaws in Eptura Archibus, building-management software, that let an attacker run commands without logging in. [10]

A flaw rated 10 out of 10 in NVIDIA's AIStore, storage for AI data, can hand over the computer it runs on. [10]

Why it matters

Each of these tools holds a company's records, so one flaw opens far more than the tool itself.

Why it matters

Rapid7 says an attacker on Archibus could read secrets and passwords out of its database. [10]

AI computing firm Andromeda loses credentials

Swipe up for the story ↑Scroll down for the story ↓

Andromeda, a company that provides computing for AI work, said it found on 13 October that someone had reached credentials inside its systems. [10]

It shut the affected accounts that day and says it has seen no misuse since. [10] It believes the break-in was part of an attack across the industry around 9 October. [10]

A limited number of customers were hit, and it found no sign anyone reached their AI models or data. [10]

Why it matters

Some of the exposed credentials were customers' own, not only Andromeda's. [10] Andromeda says customers it believes were affected have already heard from it. [10]

OpenCode fixes a flaw in its sign-in

Swipe up for the story ↑Scroll down for the story ↓

Pillar Security found a critical flaw in OpenCode, an AI tool that helps people write software, on Windows computers. [10]

A rogue outside service plugged into OpenCode could run its own code on a programmer's machine during sign-in, with no extra click. [10] The maker, Anomaly, fixed it in version 1.18.33. [10]

It comes days after OpenCode confirmed a break-in at its Console, which could have exposed users' keys for Anthropic, OpenAI and Google AI services. [10]

Why it matters

OpenCode said the earlier break-in hit 1.4% of its Console users, as part of a large attempt to copy AI models. [10] Its Windows users now need the update as well. [10]

Chrome now asks before unprotected pages

Swipe up for the story ↑Scroll down for the story ↓

Google's Chrome browser now asks permission before opening a website over plain HTTP, which sends pages without encryption. [10]

Encryption scrambles what travels between a browser and a site so nobody on the way can read or change it. [10]

Until now the warning was only for people who had switched on Chrome's strongest safety mode. [10] It is now on for every user by default. [10]

Why it matters

Anyone on the same network, such as a public Wi-Fi, can read or alter an unencrypted page, and the new question warns people before they open one. [10]

Why it matters

Google calls the change the end of more than ten years of work. [10]

How it works

Chrome asks before unprotected pages

Chrome used to open unencrypted pages without asking unless a user had chosen its strongest safety mode, and now it asks every user first.

The idea, in story 5: A strong check often keeps a weaker way round it, and attackers take that way →

Who gains

Chrome now stops to ask before opening an unencrypted page, for every user by default. [10]

Good news

Chrome now asks before opening any web page that is not encrypted, for every user, not only those who chose its strongest safety mode.

52 billion stolen browser cookies found online

Swipe up for the story ↑Scroll down for the story ↓

NordVPN, a security company, says it found 52 billion stolen cookies in leaked data online in the year to June, the Guardian reports. [11]

A session cookie is the small file a website gives a browser after login so it need not ask again. [11]

Malicious programs on a computer copy these cookies and send them to criminals. [11]

With one, a thief can enter the account without the password or a login alert, and can often skip the second check. [11]

Why it matters

NordVPN's Marijus Briedis says closing a tab does not end a session, but logging out makes the cookie useless to a thief. [11]

Why it matters

He says the malware usually hides in browser add-ons and downloaded software. [11]

How it works

52 billion stolen cookies

A website checks the password and second code once, then gives the browser a cookie so it need not ask again, and a thief with that cookie can often skip both checks.

The idea, in story 5: A strong check often keeps a weaker way round it, and attackers take that way →

Who gains

NordVPN counts 52 billion such cookies online, and each open session lets a buyer in without the password. [11]

China-linked addresses keep trying old flaws

Swipe up for the story ↑Scroll down for the story ↓

VulnCheck, a firm that tracks attacks on software flaws, says it saw attacks on five old, known flaws from three internet addresses in Hong Kong and Taiwan. [10]

The addresses appear in the US government's warning about Flax Typhoon, a hacking group linked to China. [10]

Earlier this month the FBI and the US Justice Department disrupted tools the group used to scan and break into networks. [10]

The flaws include ones in Apache web servers and XWiki, software for shared web pages. [10]

Why it matters

VulnCheck published its alert as a follow-up to the FBI's action. [10]

Why it matters

All five flaws have had fixes for a year or more, so the servers at risk are the ones never updated.

GMO asks Japan to use its new cyber powers

Swipe up for the story ↑Scroll down for the story ↓

GMO Internet, a large Japanese web company, asked Japan's government on Saturday to use new cyber defence powers against hackers who broke into one of its services. [12]

The powers took effect on 1 October, and let police and Japan's Self-Defense Forces break into attackers' servers and disable them. [12]

The hackers hit Onamae.com Desktop Cloud, which rents out servers to people who trade currencies by machine. [12]

They then demanded money, threatening to keep placing trades through accounts at over 70 trading firms. [12] GMO says it will not pay. [12]

Why it matters

GMO says this would be the first use of the powers, though it is not on the law's list of critical operators, Impress Watch reports. [12]

Why it matters

GMO will pay 5,000 yen, about $32, to every current customer and is closing the service for good. [12]

That's the whole Cyber day.

15 stories, 12 sources.