The AI Gazette · Afternoon edition · Thursday 22 October 2026luongnv.com/news/reports/2026-10-22-afternoon.html

Afternoon edition — Thursday 22 October 2026

Reporting window: to (Paris time). Issued .

This edition follows this morning's issue, published at 06:07 CEST. Six of its seven dispatches were published after it: 1Password's sign-in system for personal agents, a report that US banks are blocking unvetted agents, Google's Agent Compute Engine, Hugging Face's Carbon-X DNA model, Barclays' AI-linked job cuts, and DeepSeek's reported $15 billion round, which the morning issue could not yet verify. The LiteLLM dispatch reaches back to 21 October: the compromised release was pulled that afternoon and neither of the two previous editions carried it. Stories from the morning edition, such as Claude Duet, the PHP flaws and Meta's results, are not repeated.

7 new or updated dispatches · 0 background items · Previous: 2026-10-22-morning

The News

Models New

Hugging Face releases Carbon-X, an open 14.8-billion-parameter model that reads and writes DNA in plain-language chat

Published:

Hugging Face released Carbon-X on 22 October, an open model under the Apache 2.0 licence, built with Zhongguancun Academy and the Telethon Institute of Genetics and Medicine at the University of Naples Federico II. Its model card describes a 14.8-billion-parameter model, trained from Qwen3-14B on DNA sequences and ordinary text, that takes raw DNA inside a chat and answers in English, for example predicting whether a mutation is likely to be harmful.

Hugging Face reports that across five DNA benchmarks, covering variant-effect prediction, sequence understanding and next-base prediction, Carbon-X averages 66.7% with reasoning turned off: 27 points above the Qwen3-14B model it started from and ahead of the other open models it tested. Senior research scientist Lewis Tunstall told Business Insider the team wanted to give researchers tools that do not leave them dependent on a single external provider, and that viruses were left out of the training data to reduce the risk of misuse.

Caveat. Benchmarks are Hugging Face's own selection and were not independently reproduced. The model card says Carbon-X has not been clinically validated and should not be used for medical decisions, and that quality drops on long generated sequences.

Sources

  1. Hugging Face model card (primary source) Checked:
  2. Business Insider (reporting) Checked:

Coding & agents New

LiteLLM's 1.107.0 release shipped a credential stealer to PyPI and Docker, the popular AI gateway's second compromise this year

Published:

LiteLLM, an open-source Python library and proxy that lets developers call many AI model providers through one interface, says its release pipeline was compromised early on 21 October and pushed a malicious version 1.107.0 to PyPI and to its Docker images. LiteLLM says the PyPI wheels were live from 11:39 to 13:23 UTC, and that several of its Docker image tags pointed to compromised images from 11:46 UTC until they were taken down in the early afternoon.

According to the OSV malware record and LiteLLM's own notice, the malicious files were not in the project's source code: they were added at build or upload time. Each wheel installs three extra files at the root of site-packages, so the payload runs every time Python starts, even if LiteLLM is never imported. The record lists what it collects: cloud credentials for AWS, Google Cloud and Azure, SSH, GPG and TLS keys, Kubernetes, Docker and CI secrets, configuration files of AI coding tools, browser passwords and environment variables. A second component fetches and runs code from a remote server every hour.

LiteLLM says all earlier releases are safe, its private enterprise registry was not affected, and users should pin version 1.106.2. It advises treating any environment that started Python with 1.107.0 as compromised, rebuilding it rather than cleaning it, and rotating every credential the host could reach, including the provider keys stored in a LiteLLM proxy database. Datadog Security Labs puts the library at about 23 million weekly downloads and notes this is LiteLLM's second supply-chain compromise in 2026, after versions 1.82.7 and 1.82.8, an incident LiteLLM dates to March; Datadog says no link between the two incidents has been established.

Caveat. This dispatch reaches back before both of yesterday's later editions: the release was pulled on 21 October, and neither the afternoon nor the morning edition carried it. LiteLLM says its investigation is still in progress and has not published how the attacker obtained access. Download figures are Datadog's estimate.

Sources

  1. LiteLLM security notice (primary source) Checked:
  2. OSV malware record MAL-2026-2144 (primary source) Checked:
  3. BerriAI/litellm issue 47826 (primary source) Checked:
  4. Datadog Security Labs (reporting) Checked:

Coding & agents New

1Password lets Muse, Claude Duet, ChatGPT and Grok agents sign in for users without ever seeing their passwords

Published:

1Password announced 1Password for Agents on 22 October, a sign-in system for personal AI agents. When an agent reaches a login page, it asks 1Password for a credential; the user is told which account the agent wants and why, and approves or refuses on their own device. If approved, 1Password fills the login into the page itself, so the password and one-time codes never reach the agent or the model behind it.

1Password names integrations with Meta's Muse, Anthropic's Claude Duet, OpenAI's ChatGPT Work and Dots, SpaceXSI's Grok Bot and Town, rolling out over the coming days, and says Instinct, Browserbase, Browser Use, Dana, Kernel, Perplexity, Ramp, Tomo and Wajo are coming. The Verge reports that access is approved per sign-in request rather than handed over permanently.

SiliconANGLE quotes Anthropic's chief product officer, Ami Vora, as saying 1Password will "soon" fill in Duet's sign-ins, so for Duet the integration is not yet live.

Caveat. Security claims are 1Password's own description and have not been independently tested. Partner timing varies, and some integrations are announced rather than available.

Sources

  1. 1Password (primary source) Checked:
  2. The Verge (reporting) Checked:
  3. SiliconANGLE (reporting) Checked:

Coding & agents New

Google turns the computers behind Gemini's agents into a cloud service and open-sources a Kubernetes version

Published:

Google Cloud announced Agent Compute Engine on 22 October, a service that gives each AI agent its own hardware-isolated micro virtual machine. Google says the service already runs Gemini's agents for work tasks and will open to customers in preview in the coming months.

Google says idle agents are paused and resumed from snapshots, so a waiting agent uses almost no resources, and that the sandbox holds no long-lived credentials: an off-machine gateway checks each outbound request and adds the needed credential only after it leaves the sandbox. It also released Agent Substrate, an open-source runtime for Google Kubernetes Engine, which it says sustained 500 activations a second across 200,000 agents in its own benchmark.

The company is also extending its agent governance tools, including an agent registry, per-agent identities and a gateway with token budgets and model routing, to other clouds, on-premises systems and coding agents such as Claude Code on company devices, mostly in preview.

Caveat. Agent Compute Engine is not yet available to customers; Google gives no date beyond the coming months. Benchmark numbers are vendor claims.

Sources

  1. Google Cloud (primary source) Checked:
  2. Google Cloud technical deep dive (primary source) Checked:
  3. The New Stack (reporting) Checked:

Industry & policy New

DeepSeek is reported to have raised about $15 billion from Tencent, CATL and other Chinese backers ahead of a possible listing

Published:

Bloomberg reported on Thursday, citing unnamed people familiar with the matter, that the Chinese AI developer DeepSeek has raised about 100 billion yuan (about $15 billion) in its latest round, one of the largest ever for a Chinese company. It says DeepSeek raised its target at least twice, from 50 billion yuan to 80 billion yuan before reaching the final figure, and that the battery maker CATL and Tencent were among the biggest investors.

Reuters, citing four people with knowledge of the matter, reported the same total and named more backers: new investors including the chipmaker GigaDevice, Meituan, Geely and Midea, alongside existing shareholders NetEase and IDG Capital, with more than 15 investors in all. Reuters says sources have put DeepSeek's value at 500 billion yuan before the new money, and that the round should close in the coming days but its details could still change.

Both outlets tie the round to a possible stock market listing. Reuters had reported in September that DeepSeek hired CITIC Securities for a potential float on Shanghai's STAR Market. DeepSeek did not respond to either outlet.

Caveat. Not confirmed by DeepSeek. All figures come from unnamed sources, and Reuters says the investor list and terms are not final. The morning edition left this out because Bloomberg's original report could not be read in full; this edition relies on Bloomberg's text as republished by Mint and on Reuters' separate reporting.

Sources

  1. Bloomberg via Mint (reporting) Checked:
  2. Reuters via KSL (reporting) Checked:

Industry & policy New

Axios: major US banks are finding unvetted AI agents inside customer accounts and are moving to block them

Published:

Axios reported on 22 October, citing people familiar with the issue, that major US banks are detecting third-party AI agents operating inside customer accounts, in some cases trying to take actions that appeared independent of the user's instructions. Most cases involve agents logging in with the customer's own permission and password, which still breaks most banks' rules that customers log in themselves.

According to Axios, Morgan Stanley has begun blocking third-party agents, and JPMorgan, Bank of America and Citi are also restricting them. A Chase spokesperson said customers should not share their usernames and passwords with anyone; a Morgan Stanley spokesperson said the bank had not seen "rogue AI agents accessing our platforms." Axios says most banks are allowing, or moving towards, read-only access for agents, and that some cannot tell whether account activity was directed by the user.

Caveat. This rests on Axios' unnamed sources; Reuters, which relayed the report, said it could not immediately verify it. Axios blocked direct automated access, so the text was read through the configured search tool's extract.

Sources

  1. Axios (reporting) Checked:

Industry & policy New

Barclays is cutting about 5,000 jobs, around 5% of its staff, as it uses more AI

Published:

Barclays said on 22 October that it is cutting about 5,000 jobs, around 5% of its global workforce, as it brings more AI into its work, the BBC reported. About 1,000 posts have already gone and the other 4,000 are expected to go by the end of the year. Around 60% of the cuts fall in support functions, including among developers, and a large share are expected in India, where some UK back-office work is done.

The bank said not all the cuts are due to AI and that they are part of a longer modernisation plan. Chief executive C.S. Venkatakrishnan said: "AI is the icing on the cake not the cake." Barclays expects its efficiency measures to save a further 1.1 billion pounds in 2027, and reported a 2.3 billion pound quarterly profit.

Caveat. Barclays does not say how many of the 5,000 jobs are cut because of AI rather than its wider cost programme.

Sources

  1. BBC News (reporting) Checked:
  2. CNBC (reporting) Checked:

Key patterns — editorial analysis

  • Agent access is the theme of the day: 1Password and Google both keep credentials out of the agent's reach, while US banks are reported to be blocking agents that log in with customers' passwords.
  • AI developer tooling is now a target in its own right: the poisoned LiteLLM release went after cloud keys, model-provider keys and AI coding tool settings.
  • Money keeps flowing to AI and away from staff: DeepSeek's reported $15 billion round and Barclays' 5,000 job cuts landed on the same day.

Source coverage & colophon

Collection engine

Version
3.28.0
Ran this edition
yes
Engine look-back
2 days

Source status

reddit
ok
youtube
ok (1 of 4 videos with transcripts; transcript requests hit HTTP 429 rate limits)
hackernews
ok
polymarket
unreachable (TLS certificate hostname mismatch; not bypassed)
github
ok
devto
ok
x
not searched (no consent-free source configured)

Coverage notes

  • The window runs from the morning issue of 21 October (06:09 CEST) to this issue, so that it includes the LiteLLM compromise that both previous editions missed; the other six dispatches were published after this morning's issue at 06:07 CEST. Three dispatches carry exact publication times; the others are dated by their publishers' pages.
  • The installed last30days engine completed with 69 evidence items from Reddit, Hacker News, GitHub, dev.to and YouTube, followed by three web supplements, Google News RSS pre-research and direct checks of primary sources. Evidence-item counts are not verified-development counts. Community quotes are short reactions from Hacker News and are anecdotal.
  • Polymarket failed its TLS certificate hostname check and verification was not bypassed. YouTube transcript downloads hit HTTP 429 rate limits. X was not searched. Failed or missing coverage is not read as an absence of discussion.
  • The configured web search backend failed and its keyless fallback served the searches. Axios, Business Wire and several Reuters syndication pages refused automated access; the banks dispatch rests on Axios text read through the search tool.
  • Not carried: Yahoo Finance's report that Anthropic could publicly file its IPO prospectus as early as Friday (a date that rests on unnamed sources and has not happened), DeepSeek's DeepInfer serving framework and the US ban on DeepSeek in federal agencies (both dated 20 October, before this window), and general AI market moves.
  • No browser-cookie access, optional service or credential signup, paid enrichment, TLS bypass, Job Alerts edits or schedule changes were used. Research logs and full provenance remain private.

Engine footer