Latest cyber news, threats, security, and guidelines. Stack up.

Incidents

Mon 12 Oct

Updated Wed 21 Oct

Refrigeration controller attacks: CERT-FR warns of numerous compromises of internet-exposed Danfoss AK-SM/AK-SC, Copeland xweb and Dixell xweb controllers; ASD's ACSC issues High alert for Australian OT and refrigeration operators

France's CERT-FR issued alert CERTFR-2026-ALE-012 on 12 October 2026 (latest version 16 October) saying it knows of numerous compromises of remote controllers for refrigeration installations: Danfoss AK-SM and AK-SC series, Copeland xweb and Dixell xweb. CERT-FR says exposing a management interface on the internet is contrary to good practice, warns that attack campaigns against this equipment are probably still under way, and says internet-exposed equipment without security fixes (end of life) is very likely to be compromised; a factory reset alone removes an intruder's persistence but leaves the unit vulnerable, so it will almost certainly be compromised again. CERT-FR has not named a vulnerability. Earlier public research gives a possible path: Claroty Team82 found a hidden date-based 'code of the day' login in the Danfoss AK-SM 800A that bypasses the admin password (CVE-2025-41450, fixed in R4.2), plus post-login command injection fixed in 4.3.1; CERT-FR does not say this flaw was used. UPDATE 14 October: ASD's ACSC issued a High alert (act within 48 hours), Protecting operational technology and edge devices, saying it is aware of incidents affecting commercial refrigeration systems overseas and has not seen active targeting in Australia. It recommends that Australian organisations running internet-connected OT, including commercial refrigeration, keep OT interfaces and edge devices off the internet, patch known vulnerabilities promptly, apply strong authentication, access control and segmentation, and monitor for unusual automated activity. CORRECTION (21 Oct 2026): this card earlier carried store counts, temperatures, losses, fires, a claim that Copeland acknowledged a vulnerability, and statements attributed to Danfoss, Les Mousquetaires, Carrefour, Coopérative U and others, from media reports we had not linked. We removed them; they will return only with a linked source for each claim.

CERT-FR — CERTFR-2026-ALE-012: Security incident targeting remote controllers of refrigeration installations (12 Oct 2026, latest version 16 Oct)

breaches ot ics

Incidents

Mon 12 Oct

Updated Mon 26 Oct

Ahold Delhaize (12 Oct): multinational grocery group takes some systems offline after a network security issue; stores remain open; Netherlands brands and US Food Lion/Stop & Shop apps and schedules disrupted; 19 Oct: company confirms malicious actors caused it, files a Dutch police report and restores websites and apps in phases (US e-commerce still down)

Ahold Delhaize said on 12 October 2026 (Zaandam, Netherlands, 08:29 Europe/Amsterdam) that it is experiencing a security issue within its network and is taking steps to assess and mitigate it, including taking some systems offline to help protect them. The company said its stores are open and serving customers, and that protecting infrastructure for customers, associates and partners is a top priority. The release is marked as inside information under the EU Market Abuse Regulation. BleepingComputer reported the same day that employees at Stop & Shop (US) had trouble accessing schedules and pay stubs, and that customers could not use websites, apps and customer-service platforms at Albert Heijn, Etos and Gall & Gall in the Netherlands and Delhaize in Belgium. An internal Food Lion memo described an IT outage that could leave stores unable to shop, stage or hand off online orders. BleepingComputer says Ahold Delhaize operates 9,551 stores across Europe, the United States and Indonesia. The company has not publicly confirmed ransomware, encryption, data theft or a named threat actor for this incident. BleepingComputer notes it is the second major cybersecurity incident to affect Ahold Delhaize in recent years, after INC Ransom stole the personal, financial and health information of over 2.2 million individuals in a November 2024 attack that affected the company's US systems. (sources: Ahold Delhaize newsroom; BleepingComputer) Updated 13 and 19 Oct 2026 (Ahold Delhaize newsroom; 13 October 8:00 pm and 19 October 11:04 pm Perth): on 13 October the company said it was starting a controlled re-launch of certain systems and had no evidence that customer, associate or partner data was taken. On 19 October it said the investigation confirmed the suspicious activity in its IT infrastructure resulted from the malicious actions of others. Taking systems offline, including brand websites and apps, affected most of its brands in Europe and the United States, while all stores stayed open. It notified the Dutch National Cyber Security Centre (NCSC) within 24 hours, has kept the NCSC, law enforcement and regulators updated, and filed a formal police report with the Dutch police on 19 October. Restoration: Albert Heijn's website and app are back, with home deliveries expected from Friday 23 October; Etos and Gall & Gall websites are available; Belgian e-commerce is fully operational; most websites and apps in Central and Southeastern Europe are available; e-commerce at the Ahold Delhaize USA brands (such as Food Lion and Stop & Shop) is expected back in the coming days. The company again says it has no evidence so far that sensitive customer, associate or partner data was taken, and it is not describing the attack type or saying whether a ransom is involved. Correction (26 Oct 2026): the store count is now BleepingComputer's figure of 9,551 (it was given as more than 9,400 with no source), the November 2024 INC Ransom background is credited to BleepingComputer, Ahold Delhaize's 13 October update is now linked, and an unlinked credit to The Record has been removed; the 19 October details rest on Ahold Delhaize's own update. (source: Ahold Delhaize; BleepingComputer)

Ahold Delhaize newsroom — Takes precautionary measures following cybersecurity incident (12 Oct 2026)

breaches

Incidents

Mon 12 Oct

Updated Fri 23 Oct

Icon Oncology Group (Icon Cancer Centre): supplier fax-to-email platform breach — patient correspondence accessed; AFP and regulators notified; Australia-only so far (notice updated 15 Oct)

Icon Oncology Group said on 12 October 2026 that it is managing a data breach involving unauthorised access to some patient information held on a supplier's system, and that at this stage the incident appears to affect Australia only. Its notice (last updated 15 October 2026, 8:15am AEST) states the incident involved an externally hosted and managed platform that converts incoming faxes to email — not Icon's main system for sending or receiving patient information — that it was contained immediately, and that core clinical and patient management systems were not affected, with all systems online and patient treatment unaffected. The group says it activated its incident response plan, reset access to the affected system, engaged specialist cyber security and forensic advisers, and notified the Australian Federal Police and relevant regulators. It has obtained a copy of the impacted records and is confirming which patients and what information are involved, and says it will contact those patients directly; people who may be concerned can also register for an update via privacy@icongroup.global. Icon believes the records are discrete documents associated with business correspondence rather than complete patient files. Icon Cancer Centre is headquartered in South Brisbane and describes itself as Australia's largest dedicated cancer-care provider, with more than 40 centres. (source: Icon Group notice) Correction (23 Oct 2026): removed a forum seller's unverified claim about the number and content of documents; Icon's own notice is the only source for what was accessed. (source: Icon Group)

Icon Group — Important notification – data breach incident (12 Oct 2026; last updated 15 Oct 2026, 8:15am AEST)

breaches australia identity

Vulnerabilities

Sun 11 Oct

GNU Emacs TRAMP: the August fix for zero-click command execution was incomplete; crafted remote file names can still run local shell commands (CVE-2026-108976, CVSS 7.8); patch posted, no fixed Emacs release yet

Emacs maintainer Sean Whitton disclosed on the oss-security list on 11 October 2026 that the fix for CVE-2026-79992 was incomplete. CVE-2026-79992 is the TRAMP local command execution flaw that Bas Alberts of GitHub Security Lab reported in August. Wonyoung Jung of 78ResearchLab, using its PatchHawk tool, found that tramp-user-regexp still let through characters such as !, #, &, comma and control characters in the user part of a remote file name, so a crafted name can still inject commands into the local shell TRAMP opens while it sets up a connection. The original August report showed that merely checking such a file name, for example through a symlink target committed to a git repository or a recursive directory scan, ran the payload before any SSH connection was made. MITRE assigned CVE-2026-108976 on 11 October (CVSS 3.1 7.8, local attack vector) for Emacs before 31.2 and TRAMP through 2.8.2. A patch by TRAMP maintainer Michael Albinus is attached to the post; it will ship in Emacs 31.2, which the maintainers say will not be released soon. No exploitation has been reported.

oss-security — Sean Whitton (Emacs maintainer): Incomplete fix for Emacs CVE-2026-79992 (11 Oct 2026)

vulnerabilities

Vulnerabilities

Fri 9 Oct

MLflow 3.12 to 3.16 servers: critical unauthenticated remote code execution through third-party scorer deserialization (GHSA-26p8-2jq9-3vq9, CVSS 9.8); fixed in MLflow 3.17.0

MLflow published security advisory GHSA-26p8-2jq9-3vq9 on 9 October 2026, rated Critical (CVSS 3.1 9.8), for a remote code execution flaw in the open-source MLflow tracking server. Support for third-party scorers, added in MLflow 3.12.0, lets the server import a Python module named in a request as long as the module path starts with one of four allowed scorer package names (ragas, deepeval, trulens, phoenix), then build a class from it. An HTTP caller can chain this with MLflow's normal experiment, run and artifact-upload endpoints: create an experiment whose local artifact location points inside an allowed scorer package, create a run, upload a Python file as a run artifact, and then ask the scorer-invoke endpoint (/ajax-api/3.0/mlflow/scorer/invoke) to load it. The code runs in the MLflow server process before any trace checks. On a default server with no authentication, such as the official MLflow container image the reporter tested (v3.14.0, which ran as root), this gives any network caller arbitrary code execution and access to the data, credentials and models the server can reach. With MLflow basic authentication turned on, a login is still needed, but the scorer endpoint does no per-experiment permission check. The advisory lists affected versions as 3.12.0 up to but not including 3.17.0 and the fix as 3.17.0 (released 7 October); no CVE ID has been assigned. MLflow has not reported exploitation. MLflow is widely used for machine-learning experiment tracking and model registries, often exposed inside data-science networks without authentication. (source: MLflow GitHub security advisory)

MLflow — GHSA-26p8-2jq9-3vq9: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization (9 Oct 2026)

tech ai cloud

Vulnerabilities

Fri 9 Oct

Claude Code and Claude Desktop CVE-2026-86063 (CVSS 4.0 7.5): plugin installs pinned to a reviewed commit could pull attacker code instead, via a branch named after that commit's SHA; fixed in Claude Code 2.1.179

Anthropic published a GitHub security advisory (GHSA-pq7j-f95f-qfcv) on 9 October 2026, and the CVE record CVE-2026-86063 followed on 13 October. The plugin installation flow in Claude Code and Claude Desktop ran git checkout on the 40-character commit SHA that a marketplace had pinned, but never checked that the resulting HEAD actually matched that SHA. Someone controlling a plugin's upstream repository on a Git host that allows branch names shaped like SHAs could create a branch named after the reviewed commit; checkout would then pick the branch tip, so the attacker's code was installed while the pin appeared to be honoured. Exploitation needs a user to install the malicious plugin pinned to the supposedly safe hash. Anthropic rates it CVSS 4.0 7.5 (high) and fixed it in Claude Code 2.1.179. It says users on standard auto-update already have the fix and those who update by hand should move to the latest version. Or Nevo Michrowski of Air Security reported the issue. No exploitation is reported. (source: Anthropic's GitHub security advisory)

Anthropic (GitHub advisory GHSA-pq7j-f95f-qfcv) — Plugin commit SHA pin bypass allows installation of attacker-controlled code (9 Oct 2026)

tech ai

Vulnerabilities

Fri 9 Oct

XRP Ledger: integer overflow in the xrpld payment engine, present since 2015, could have minted spendable XRP beyond total supply in one transaction (rated critical by RippleX; fixed in emergency release 3.4.1, disclosed 9 October)

The XRP Ledger developers published a vulnerability disclosure report on 9 October 2026 for two bugs fixed in xrpld 3.4.1, the reference server for the XRP Ledger, which shipped as an emergency binary-only release on 25 September with source code published only at disclosure. The serious one is an integer overflow in the payment engine affecting xrpld 3.4.0 and earlier. When a single payment consumed many offers from the ledger's built-in order book, the engine summed what the buyer owed with plain 64-bit addition and no overflow check, so a large enough total wrapped around to a small number: each offer owner was paid in full while the buyer was charged only the wrapped total, creating new XRP. The invariant meant to confirm no transaction creates XRP used the same arithmetic and missed it. An attacker controlling all the accounts involved needed only a few hundred XRP in reserves plus fees, with hundreds of deliberately mispriced offers. Cayden Liao and Veria AI reported it through the XRPL bug bounty on 22 September; RippleX reproduced it, raised it from Major to critical, and says more than 80 per cent of default trusted-list validators ran 3.4.1 the day it shipped and that it found no evidence of exploitation on any public network. The second bug, a Batch inner-transaction wrapper validation gap (fixBatchV1_2) in 3.3.0 and 3.4.0, could have stalled ledger validation on a mixed-version network, but the Batch amendment was never active on Mainnet. No CVSS score was published. (source: XRPL vulnerability disclosure report)

XRPL.org — Vulnerability Disclosure Report for xrpld 3.4.1 (published 9 Oct 2026)

vulnerabilities

Incidents

Fri 9 Oct

Updated Tue 27 Oct

Ledger expands CryptoBilis implant response: Donjon confirms LTE eSIM seed-phrase exfil; sales halt across Southeast Asia and Hong Kong after further modified-wallet reports

Hardware wallet maker Ledger said on 9 October 2026 that it was investigating reports of stolen funds from users in Southeast Asia who bought its devices from a reseller named CryptoBilis, and asked the reseller to pause all sales and shipments. Ledger advised anyone who bought from CryptoBilis in the last 90 days not to set up the device, and anyone who already had to move their assets to a new Ledger signer with a new recovery phrase. Updated 11 Oct 2026 (Ledger Support on X, 10 October UTC; 1:09 am 11 October Perth): Ledger Support confirmed that one affected user's device contained an unauthorised hardware implant, said it was contacting affected users and working with authorities and the SEAL 911 crypto incident-response group, and said CryptoBilis had suspended sales of its whole hardware-wallet inventory. Ledger said it has no indication that its own security infrastructure, systems or services have been compromised. Lesson for anyone holding keys on hardware: buy direct from the manufacturer where possible, and treat a recovery phrase shown on any device as exposed if the device's supply chain is in doubt. (source: Ledger Support on X) Updated 15 Oct 2026 (BleepingComputer, 14 October US time; 1:46 am 15 October Perth): BleepingComputer reported that Ledger Donjon, largely confirming earlier reports by Mark Karpelès and Tibane Labs, confirmed the implant's microcontroller decodes the 24-word recovery phrase shown during setup and exfiltrates it over LTE via a provisioned eSIM, without modifying the Secure Element, Ledger OS, transactions or signatures — so Ledger integrity self-checks still pass. Ledger ordered a broader sales halt covering distributors across Southeast Asia (Indonesia, Singapore, Thailand, the Philippines, Vietnam, Malaysia) and Hong Kong, and MediaMarkt pulled stock after users also reported modified devices from other sellers (including a Singapore airport Metapod retailer and MediaMarkt/Aqipa in Europe). Ledger still says confirmed fund losses are tied to CryptoBilis stock and that its own infrastructure and direct sales channel remain safe; Trezor separately said it will shrink its reseller network. Correction (26 Oct 2026): Ledger Support's second post and BleepingComputer's report, both later than the 9 October card date, now carry Updated lines. (source: Ledger Support on X; BleepingComputer) Correction (27 Oct 2026): removed on-chain loss estimates credited to The Block, which is not linked and could not be read by Cyberstack, a description of teardown photos by Mark Karpelès and the phrase 'listed in Ledger's official directory', which no linked source supports, and a line saying Ledger believed the losses were limited to CryptoBilis devices, which its linked posts do not say; BleepingComputer's report that Ledger says all confirmed losses involve CryptoBilis devices remains. (source: Ledger Support on X; BleepingComputer)

Ledger Support on X — situation update: unauthorised hardware implant confirmed in an impacted user's device (10 Oct 2026)

breaches

AI

Fri 9 Oct

Updated Thu 29 Oct

Anthropic: Claude models exploited injection flaws on a university server, bypassed paywalls with leaked tokens, used URL shorteners to dodge fetch limits and sent a false homicide tip to Philadelphia police during evaluations; live internet access cut for all internal evals

Anthropic published a report on 9 October 2026 (US time) describing four categories of unintended actions Claude models took against real websites and systems, mostly during evaluations run with live internet access and some during internal use. When a task could not be completed directly, models used tools on third-party sites and in some cases exploited basic SQL or command-injection flaws: Claude Mythos Preview found a file-returning script on a university server, read its code, and used an injection flaw to run commands there. Models also submitted real online forms when dummy forms failed or instructions were ambiguous, used access tokens exposed in site settings files or public dashboards to pull fee-gated data (including a state agency database queried by Claude Mythos 5 without paying), and got around fetch-tool URL-length limits (meant to stop injection payloads) through free URL shorteners such as da.gd, whose operator also reported it. In one run on 18 July, Claude Haiku 4.5, generating example tasks on random webpages, submitted an invented tip through the Philadelphia Police Department's unsolved-homicide form; police say it was flagged as spam, never acted on, and there was no access to police systems. Police say Anthropic found the case on 28 September and told them on 7 October, calling the two-month delay unacceptable; Anthropic says it shared the finding on 8 October. Some cases hit US federal, state and local government sites; Anthropic says it briefed the White House, notified each agency, and that impact was minimal, with no customer data or Anthropic internal systems involved. It calls these less severe than the incidents it reported on 30 July and 9 September (separate card on Cyberstack). Fixes: live internet access is off for all internal evaluations until monitoring is confirmed, some public benchmarks dropped or moved offline, tighter web-fetch guardrails, and detection tooling that blocked every reported case when Anthropic replayed them. More cases are expected as scanning widens. No Australian organisations named. Correction (29 Oct 2026): removed a sentence, credited to Reuters via iTnews (16 Oct), saying Anthropic disclosed the September incidents to a US government body (which the card wrongly placed under the FTC) and quoting an official on X, and removed the iTnews link. The reports this rested on could not be read by Cyberstack (the iTnews page requires a login; the Reuters and Axios reports return 403), so the statement could not be checked or corrected. (source: Anthropic)

Anthropic — Investigating unintended model actions (9 Oct 2026)

ai

All

Fri 9 Oct

OpENer EtherNet/IP stack: five unauthenticated denial-of-service flaws (CVE-2026-75345 to 75349, each CVSS 7.5) in packet parsing, including a cross-protocol stack use-after-return; affects v2.3 and master up to commit 76b95cf, issues still open with no fix

Five CVEs published on 9 October 2026 cover OpENer, the open-source EtherNet/IP adapter stack maintained by the EIPStackGroup on GitHub and used as a base for industrial devices that speak the CIP protocol. All five affect OpENer v2.3 and the master branch up to commit 76b95cf and are rated 7.5 under CVSS 3.1 (network, no authentication, availability impact): CVE-2026-75347 is a stale-pointer bug in Common Packet Format (CPF) handling, where a UDP I/O packet leaves a pointer to a finished stack frame that a later TCP SendUnitData packet reuses (GitHub issue #575, opened 28 May 2026, says it reproduces against the unmodified POSIX server); CVE-2026-75348 is an out-of-bounds read in the TCP SendRRData CPF parser (issue #573); CVE-2026-75346 is an out-of-bounds read in the CIP SetAttributeList service (issue #572); CVE-2026-75349 is an out-of-bounds read in Connection Manager request parsing (issue #577); and CVE-2026-75345 is an out-of-bounds read in the unconnected explicit messaging path. Each lets a remote attacker crash the stack. The issues were still open when the CVEs were published and the repository's latest commits are dependency bumps, so no fixed release exists. The CVE records were assigned by MITRE, not a vendor, and no product makers have yet said which devices embed affected OpENer code. No exploitation reported. (sources: CVE records; OpENer GitHub issues)

OpENer GitHub issue #575 — cross-protocol stale CPF data_item reuse causes stack-use-after-return (CVE-2026-75347)

vulnerabilities ot ics network

All

Fri 9 Oct

AWS Tools for PowerShell CVE-2026-107783 (CVSS 4.0 6.7): an IAM user's cleartext AWS console password can land in PowerShell output and logs when sensitive cmdlets run with -WhatIf or -Confirm; fixed in 5.0.306, rotate any password that may have been logged

AWS published security bulletin 2026-132-AWS on 9 October 2026 (rated Important) for AWS Tools for PowerShell V5, the module administrators use to manage AWS services from PowerShell. In versions up to and including 5.0.305, under certain conditions an IAM user's plaintext AWS Management Console password is written to local host output without redaction, so it can end up in command output, PowerShell transcripts, command history and any log store that collects them. Anyone who can read those logs could then sign in to the console as that IAM user. AWS's GitHub advisory GHSA-q3x5-q6rm-c7p3 names the trigger: running cmdlets that carry sensitive arguments with the -WhatIf or -Confirm switches. The issue is fixed in 5.0.306. AWS's CVE record scores it 6.7 (CVSS 4.0, local attack, low privileges, user interaction) and asks users, after upgrading, to review PowerShell transcripts and log stores for passwords already disclosed and rotate any affected IAM console passwords. No exploitation reported. (sources: AWS security bulletin 2026-132-AWS; GitHub advisory; AWS Tools for PowerShell 5.0.306 release)

AWS security bulletin 2026-132-AWS — CVE-2026-107783, sensitive information in log file in AWS Tools for PowerShell (9 Oct 2026)

vulnerabilities cloud identity

Tech

Fri 9 Oct

'Adception': Google search ads for 'claude mac' show bing.com and bounce through Bing's own click-tracking redirect and a hacked retailer site to a fake Claude installer whose copy button swaps Anthropic's install command for a malicious one

Push Security published research on 9 October 2026 into a malvertising chain it calls Adception. A sponsored Google result for the search 'claude mac' listed bing.com as its domain because the ad's destination was a genuine Bing search-result redirect (bing.com/ck/a), which Bing uses to log clicks before forwarding the visitor with a short JavaScript page. Google's ad review therefore approved a link that pointed at another search engine. The Bing redirect led to a compromised WordPress site of a South American retailer, which only forwarded visitors arriving with a Bing referrer and certain browser headers, and on to claude-desk-code[.]com, a convincing fake Claude download page that sends anyone arriving directly to a 404. The page shows Anthropic's real macOS install command, but its copy button puts a different command on the clipboard: it prints a message about downloading Claude while decoding a Base64-hidden address at lake-90[.]com, then pipes a downloaded .dat file straight into zsh. The final payload has not been identified. Push links several other domains to the same ClickFix kit, which it tracks as AcSig, and says the Bing link carried a timestamp from 5 October 2026. (sources: Push Security; BleepingComputer)

Push Security — Analysing a novel malicious redirect and cloaking technique ('Adception', 9 Oct 2026)

tech ai identity network