← Back to the briefing

Ivanti chain gets root on patched VPNs; fridge alert grows

5 stories4 min read4:25 listen

CERT-FR adds Copeland and Dixell kit, Ledger explains its LTE implant, and LiteLLM gets a fix.

Listen to this edition.

Narrated using an AI voice.

Read the transcript

Morning. This is It's probably nothing. Today we've got a VPN zero-day chain that Ivanti's own integrity tool can't see, a supermarket fridge campaign that now involves more than one vendor, an AI worm forecast, and a hardware wallet that phoned home over LTE.

Starting with Ivanti. It's disclosed an authentication bypass in Connect Secure, says it knows of limited exploitation, and CISA added it to the known exploited list on the thirteenth. The uncomfortable bit is Volexity's write-up. It says an actor it tracks as UTA0576 chained that bypass with a remote code execution bug and a privilege escalation, and got unauthenticated root on an appliance that was fully patched at the time. Volexity dates the activity from the third of October, and Defused told BleepingComputer it saw first signs on the first.

The privilege escalation still isn't fixed, and Ivanti says that's coming in the next few weeks. The exploit patches library code in memory only and puts back the config it touches, so the Integrity Checker sees nothing. No web shell either. Then the actor went after AD credentials, LAPS passwords and BitLocker recovery keys, and trimmed the logs. So Ivanti's advice to run the checker regularly sits a bit awkwardly here. A clean scan doesn't clear you. If you run Connect Secure, patch, but treat whether you were hit since early October as a forensics question, and I'd be thinking about those secrets too. Worth saying Volexity's findings describe one actor.

Next, the French supermarket fridge attack from yesterday has grown. CERT-FR now says it knows of numerous compromises of Danfoss remote controllers, and its latest revision adds Copeland and Dixell XWEB kit. It thinks campaigns are probably still under way, warns that an exposed end-of-life unit is very likely to get done again, and says a factory reset alone doesn't help. Cybernews, citing La Dépêche, reports a Leclerc near Albi running Dixell gear had a major refrigeration failure early on Tuesday.

So this isn't one vendor's legacy firmware problem anymore. It's internet-exposed fridge controllers, full stop. CERT-FR hasn't named victims, an attacker or a vulnerability, and the access method isn't confirmed. Exposure counts vary, from about twenty-nine hundred to nearly five thousand Danfoss hosts depending on who you ask. The advice is pleasingly concrete though: get them off the internet, check the config, especially defrost schedules, and bring access back only through a VPN. My favourite detail is checking your insurance terms before cutting the contractor's data feed. That's real incident response talking.

On the AI front, Anthropic's Frontier Red Team reckons small models may be months away from self-replicating on cheap devices like off-brand Android TV boxes. A nine-billion-parameter model got inference running on eight of nine hardware types. In a deliberately simplified worm test over open ADB on emulated Android, GLM-5.2 and stronger models managed end-to-end replication, while smaller ones could do the steps but fumbled chaining them. Anthropic calls this an upper bound because the exploit step was trivial, and it's a forecast, not an outbreak. Still, a slow worm with no central off switch is a properly annoying shape of problem. The defence is boring: don't leave ADB open to the network.

Then Ledger. According to The Record, Ledger says devices sold through the Southeast Asian reseller CryptoBilis had hidden implants that read the screen during setup, grabbed the twenty-four-word recovery phrase and sent it out over LTE on an embedded eSIM. Funds were drained on the ninth. Ledger hasn't confirmed total losses, though SecurityWeek links an eighty-six-million US dollar heist to it. And Genuine Check can't rule out tampering that leaves the secure chip alone, which is rather the point. If you bought from that reseller, Ledger says don't set up unused devices, and if you already have, move funds to a new signer with a new phrase.

Last one. Check Point found two LiteLLM bugs. One lets even a read-only user take over the gateway, with file access and code execution shown in a test setup. The other lets authenticated users redirect requests to their own server and harvest provider API keys. An AI gateway is basically a key vault with a dashboard, so read-only meaning admin, actually, isn't ideal. No in-the-wild exploitation reported, and it's fixed from 1.83.9.

That's it for today. Probably nothing. Catch you tomorrow.

Don't forget, all our threat intelligence comes from Mallory dot A I. If you want intelligence your team can act on, reach out for a chat.

The takeaway

Today has a VPN zero-day chain that Ivanti's own integrity tool can't see, and a supermarket fridge campaign that now involves more than one vendor. There's also an AI worm forecast and a hardware wallet that phoned home over LTE.

01

Ivanti Connect Secure chain reached root on a patched box, and one link is still unfixed

Ivanti has disclosed CVE-2026-104935, an authentication bypass in Connect Secure, and says it knows of limited exploitation. CISA added it to KEV on 13 October. Volexity's write-up is the uncomfortable part. It says an actor it tracks as UTA0576 chained the bypass with an RCE (both covered by that CVE) and a privilege escalation. That gave unauthenticated root on an appliance that was fully patched at the time, running 22.8R2.4. Volexity dates the activity from 3 October, and Defused told BleepingComputer it saw first signs on 1 October.

The privilege escalation, which is in how the dsinvoked broker trusts DSCache data, isn't fixed yet. Ivanti plans a fix in the coming weeks. The exploit patches library code in memory only and restores the config data it changes, so the Integrity Checker Tool sees nothing, and Volexity found no web shell. The actor then went after AD credentials, LAPS passwords and BitLocker recovery keys, and deleted entries from the debug and Linux audit logs.

Ivanti's advice to run the ICT regularly sits a bit awkwardly next to that. A clean scan doesn't clear you here.

Worth asking

SecurityWeek lists fixes in 22.8R2.5, 25.1.1.2, 25.1.3.0 and 25.1.3.1. If you run ICS, patch, but treat 'were we hit since early October?' as a forensics question. Personally, I'd be thinking about the secrets it was after, too.

Volexity's chain findings describe one actor. 'Limited exploitation' is Ivanti's description. BleepingComputer says Shadowserver tracks more than 5,500 exposed ICS instances, but it's unknown how many are honeypots or already secured.

Sources 5
02

CERT-FR says fridge controller compromises are 'numerous' and adds Copeland and Dixell XWEB

Quick recap: this is the French supermarket refrigeration attack from yesterday. CERT-FR's alert CERTFR-2026-ALE-012 now says it knows of numerous compromises of Danfoss AK-SM and AK-SC remote controllers. Its 13 October revision adds Copeland XWEB and Dixell XWEB to the targeted kit. CERT-FR thinks campaigns are probably still under way. It also warns that an exposed end-of-life unit is very likely to be compromised again, and that a factory reset alone doesn't help. Cybernews, citing La Dépêche, reports that an E.Leclerc near Albi running Dixell equipment had a major refrigeration failure early on Tuesday.

So this has stopped being one vendor's legacy firmware problem. It's now about internet-exposed refrigeration controllers in general. CERT-FR's advice is pleasingly concrete: remove internet exposure, check the config (especially defrost schedules), and restore access only through a VPN. Filtering to contractor IPs is acceptable only as a stopgap. It also says to check your insurance terms before cutting data feeds to the refrigeration contractor, which is exactly the kind of detail only real incident response produces.

Worth asking

If you have AK-SM, AK-SC or XWEB units anywhere near a public IP, this is worth chasing down this week.

CERT-FR names no victims, attacker or CVE, and the access method is unconfirmed. Exposure counts differ: Cybersecuritynews found 4,980 Danfoss hosts on Shodan, more than half of them in France, while Cybernews cites about 2,900. A claim that the password was simply the current date is unverified.

Sources 5
03

Anthropic thinks small models may soon be able to worm across cheap IoT

Anthropic's Frontier Red Team says small models may be months away from self-replicating on commodity devices such as off-brand Android TV boxes. In its tests, a 9B model got inference running on 8 of the 9 hardware types. In a deliberately simplified worm test, spreading over unauthenticated ADB across 8 GCP nodes running an Android 15 emulator, GLM-5.2 and stronger models managed end-to-end replication. Models of 30B and under can do many of the steps but fumble chaining them. Anthropic's rough trend fit puts small models at GLM-5.2's level by the end of 2026.

This is a forecast, not an outbreak, and Anthropic itself calls the result an upper bound, because the exploit step was trivial. But a slow worm with a doubling time of days and no central off switch is a properly annoying shape of problem. The defence is the boring one: don't leave ADB open to the network.

Sources 3
04

Ledger: CryptoBilis-sold wallets read the seed phrase off the screen and sent it over LTE

According to The Record, Ledger said on Tuesday that devices sold through Southeast Asian reseller CryptoBilis had hidden implants that read the display during setup. They picked out the 24-word recovery phrase and sent it out over LTE using an embedded eSIM. Funds were drained on 9 October. Ledger says it hasn't confirmed total losses. SecurityWeek's headline links a US$86 million heist to the implant. The Defiant notes that Genuine Check can't rule out tampering that leaves the secure chip intact, which is rather the point of the attack.

Worth asking

Ledger says CryptoBilis buyers shouldn't set up unused devices and should contact support. Anyone who has already set one up should move funds to a new signer with a new recovery phrase.

Ledger's posts weren't read directly. Claims that tampered devices came through other channels are unverified.

Sources 4
05

LiteLLM bugs let a read-only user take over the gateway and its provider keys

Check Point Research disclosed CVE-2026-35029 and CVE-2026-59823 in LiteLLM. IT Security Guru says the first is a missing PROXY_ADMIN check on /config/update, combined with loosely checked dashboard session tokens. Check Point says it let even read-only users take over the gateway, and it demonstrated file access and RCE in a test environment. The second let authenticated users point gateway requests at their own server and collect AI provider API keys. Both are fixed in 1.83.9 and later.

An AI gateway is essentially a vault of API keys with a dashboard bolted on, so a read-only role meaning 'admin, actually' is not ideal.

Worth asking

If you run LiteLLM below 1.83.9, it's worth upgrading.

No in-the-wild exploitation has been reported, and the CVSS scores weren't verified.

Sources 3

See you tomorrow.

Read online, listen in your podcast app, or get the daily email.

Choose how to follow IPN →