Frontier prices fell by half on Tuesday. The same day, next/og got a 9.5.

On 24 September Anthropic expanded which refusals are billed to include refusals that arrive before any output, when stop_details.category is bio, frontier_llm or reasoning_extraction, which it describes as the categories where it measures low volumes of false positives. Mid stream refusals were already billed. The newly billed refusals are charged at the rates of the model that ran them. Refusals before output in other categories are still not billed, fallback credit is unchanged, and the change applies on all platforms.

OSV records MAL-2026-16476 and MAL-2026-16475, both published 23 September, describe malicious versions of the npm package memos-cloud-openclaw-plugin under the memtensor scope, at 0.1.21, 0.1.23 and 0.1.25, and of the PyPI package memoryos at 2.0.34. Both carry a Go implant called sckit that runs when the package loads. OSV says it targets .npmrc, .pypirc, .git-credentials, .netrc, SSH private keys, .vault-token and token caches, and collects credentials from the home directory and sends them to servers under skyleen[.]fr. In GitHub Actions it appends a BASH_ENV entry to GITHUB_ENV to capture PyPI publishing tokens. An open issue on the project repository, filed by an outside researcher, says the package's npm publish token appears to have been compromised. The maintainers have not publicly commented.

Brevo published a post mortem on a 14 September incident in which, in its words, an attacker used a compromised Brevo Cloudflare API key to deploy a Cloudflare Worker on its account. Brevo says the Worker injected a malicious script into pages of brevo.com and sibforms.com and into three JavaScript files that customers embed on their own websites, showing selected visitors a fake Cloudflare human verification page that told them to press Win+R and paste a command. It gives the impact window as 15:01 to 20:30 UTC, with the lure live on the listed customer URLs from 16:07. Brevo states that app.brevo.com was not affected and that no Brevo systems were modified at their source, the content being altered in transit at its CDN edge. The stated root cause is a long lived Cloudflare API key with full account permissions stored in application source code.

On 24 September Cloudflare disclosed a vulnerability affecting Cloudflare Containers and Cloudflare Sandboxes, which is built on Containers. Cloudflare says it would potentially have allowed a customer with a Workers Paid account to recover residual data from storage blocks previously used by other customers' Containers on the same underlying host, potentially exposing filesystem metadata, directory structures, database pages and application data. Oren Yomtov of Accomplish reported it on 4 September, fixes finished rolling out on 7 September, and cleanup of affected cached snapshots completed on 19 September. Cloudflare says it has no evidence that customer data has been compromised, and that remediation does not require any further action by Cloudflare customers.

GitHub added an npm token permission level called read and write, stage only. A workflow uses npm stage publish to submit a version, and npm rejects direct npm publish attempts with that token even if it is configured to bypass two factor authentication for automation. A maintainer then reviews and approves the release with 2FA. The token keeps other package write permissions, including moving dist tags and deprecating versions. GitHub says npm is targeting January 2027 to remove direct publishing through tokens that bypass 2FA.

Baselayer, which helps financial institutions verify businesses and assess fraud risk, raised a $35M Series A led by M13, with Picus Capital, Torch Capital, Afore Capital and Matt Thompson of Socure participating. The company declined to disclose its valuation. Its current product does Know Your Business verification by combining business identity, credit and fraud data, and it is building what it calls Know Your Agent technology to check whether an AI agent is authorised to act for a person or a business.

From 1 October 2026 apps distributed in the EU fall under one set of terms. The per install Core Technology Fee is replaced by a 5 percent Core Technology Commission on digital transactions in apps distributed outside the App Store, and the Initial Acquisition Fee and Store Services Fee are eliminated. Apple lists commission of 26 percent on Apple In-App Purchase, or 15 percent for Small Business Program participants, 20 percent and 10 percent for alternative payment processing inside the app, and a Store Services commission of 15 percent and 10 percent on out of app offers. Developers select their payment options and must maintain those options for 12 months. Account Holders have to review and agree to the updated licence agreement.

GitHub published a timeline for removing the ssh-rsa signature type, meaning RSA keys signed with SHA-1, along with the diffie-hellman-group-exchange-sha256 key exchange. All new RSA SSH keys uploaded after 14 October 2026 must be at least 3072 bits, for both signing and authentication. Brownouts follow on 4 November and 9 December 2026. The same 14 October date enables mlkem768x25519-sha256 on github.com. The changelog also prints a final removal date of January 13, 2026, which falls before the brownouts listed above it, so we are not quoting a year for the removal until GitHub corrects the entry.

The Gemini Developer API pricing page lists Gemini 3.8 Flash input at $0.75 through 31 December 2026 and $1.50 starting 1 January 2027, with output going from $3.75 to $7.50 per million tokens on the same date. Gemini 3.7 Flash and 3.6 Flash carry identical figures. The same date raises both 3.8 TTS models, both Gemini Robotics ER 2 previews, and context caching, which goes from $0.075 to $0.15 per million tokens on 3.8 Flash. Gemini 3.5 Flash-Lite at $0.30 and $2.50 has no scheduled increase, and neither does any Pro tier.

GitHub published what it calls the final notification that Node 20 is no longer available on GitHub Actions runners. Runners now use Node 24 for JavaScript actions, maintainers must set an action's runs.using value to node24 and cut a new release, and the temporary ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION opt out is no longer available. GitHub also flags that Node 24 is incompatible with macOS 13.4 and earlier and has no official ARM32 support, so self hosted runners on those systems are no longer supported.