The buyer, NordLine, is a recently established subsidiary of Russia’s second-largest natural gas producer, Novatek, Kommersant reported.

Well, this is kinda depressing, courtesy of Jason Zweig’s father:

There are three ways to make a living:

1) Lie to people who want to be lied to, and you’ll get rich.

2) Tell the truth to those who want the truth, and you’ll make a living.

3) Tell the truth to those who want to be lied to, and you’ll go broke.

I aim for #2. But maybe society needs more of #3 and, it goes without saying, a whole lot less of #1. (via df)

Tags: how to · Jason Zweig · working

Your customer service agent just wrote to a database it should have been reading from, and nobody told it to do so. Somewhere upstream, a poisoned support ticket had convinced the agent that the user was an admin, and being helpful, it obliged. This is the working day for anyone running autonomous AI in production. Prisma AIRS from Palo Alto Networks Networks sits in the middle of that traffic, inspecting tool calls and network flows rather than only the natural-language prompts on the surface, and catching the moment when an agent stops chatting and starts acting. Palo Alto Networks calls this shift "agents with hands" — models that can hit APIs, query databases, and execute tasks without a human in the loop. The convenience opens a lethal trifecta of private data access, exposure to untrusted content, and an outbound channel; none of these is dangerous in isolation, but combined they describe the route by which data quietly leaves your network. Multi-agent setups compound the problem, because east-west traffic between agents means a hallucination in one place can ripple through the entire chain. Standardized connectors offer no defense here: protocols like MCP describe how an agent talks to a tool, but say nothing about whether the request is legitimate in the first place. The named attacks grow more creative by the week. Memory poisoning, for instance, plants instructions that an agent learns and executes weeks later, while "confused deputy" attacks trick a read-only agent into writing. Rugpulls are nastier still: a tool that has worked reliably for months — long enough to earn trust — one day begins quietly siphoning data, after the organization has come to depend on it. None of these are theoretical, and all of them slip past keyword-based guardrails. Amazon Bedrock Guardrails and similar text filters work well enough for governance and content safety, but they will not catch SQL injection buried inside a tool payload, nor will they contain the dynamic reasoning of an autonomous agent. Prisma AIRS is built to take a second pass, watching the payloads themselves and killing connections when an agent suddenly demands admin privileges. The same approach blocks memory-poisoning attempts and tool-schema extraction before the malicious instruction ever lands. Genuine protection in an agentic AI environment depends on knowing where to look for hidden risks. Shadow agents accumulate inside any reasonably sized estate, inactive identities cling to permissions long after the projects that required them have shipped, and east-west traffic that historically passed unobserved through enterprise datacenters now demands scrutiny. Discovering those exposures before an attacker does requires a new generation of tooling. Agentic AI is moving quickly while the threat models that should constrain it are still being written. The sensible response is to treat the security layer the way you treated network security in 2010 — assume the perimeter is already inside, and watch what the agents do rather than only what they say. Sponsored by Palo Alto Networks.

Yet another aggrieved bug hunter has leaked a vulnerability affecting a Microsoft product after becoming disillusioned with the company’s handling of security reports. Ammar Askar dropped a proof of concept (PoC) exploit for a Visual Studio Code (VS Code) flaw within just an hour of disclosing it to “an old contact” at the open source platform, according to his account of things. The vulnerability he exposed involves attackers configuring repos, either of their own making or those they have compromised separately, to push malicious VS Code extensions via its Workspace Recommendations feature, which then steal OAuth tokens they can then use to read/write public and private GitHub repos. It affects anyone who has ever used github.dev, a feature that allows users to open a GitHub repo in a browser-based version of VS Code. Askar said that the feature is enabled by github.com passing an OAuth token over to github.dev and, crucially, this token is not limited to the repo from which github.dev was spun up. It means that this token can hand an attacker access to any other repo – public or private – to which the target also has access. The exploit is contingent on an attacker being able to modify a repo’s .vscode/extensions.json file and recommending an attacker-controlled extension for the browser-based VS Code instance. In normal scenarios, a pop-up would appear asking for a user to accept the installation of this extension, potentially tipping them off to foul play. However, because of the way in which the attacker delivers the repo to the target, they already have a Jupyter Notebook file running in the target’s github.dev before the extension is installed. The attacker must initially get the target to open their repo using a github.dev link that points to this ipynb file, which VS Code immediately opens inside a Webview. Inside the Jupyter Notebook is a hidden HTML snippet inside a Markdown cell, which when loaded allows attacker-controlled JavaScript code to run. This code fires a simulated keyboard shortcut, which VS Code bubbles up to the main editor, tricking the system into automatically accepting the malicious extension popup. The attaker-controlled extension is then running with access to the browser environment, and steals the OAuth token, which can be used to read and change any public or private repo. Askar said past negative experiences with Microsoft Security Response Center (MSRC) influenced his decision not to go through the typical responsible disclosure process, publishing the PoC roughly an hour after tipping off his GitHub contact. “To summarize the last time I interacted with MSRC regarding reporting a VSCode bug, it was a horrible experience where they silently fixed the bug I pointed out without any credit,” he wrote. “They also marked it as not having any security impact. As I mentioned in that post, going forward I would be doing full public disclosure for any security bugs I found in VSCode. Taking a look at a recent report by Starlabs on a VSCode XSS bug marked as ineligible and low severity, it doesn’t look like MSRC has gotten any better about VSCode bugs. “I’m sure the VSCode team would have appreciated a longer heads up on this to come up with solutions. There is legitimately a UI/UX balance here that needs to be struck with the security concerns. To those folks, I am sorry, but this is one of the few levers I have to try to influence MSRC and the security posture of VSCode. Finding and fully developing security bugs into proof-of-concepts like this takes time and effort on the part of security researchers that should not be disrespected or taken for granted.” Askar’s approach is reminiscent of a researcher who goes by Nightmare Eclipse, a suspected former Microsoft employee who has attracted a great deal of attention in recent weeks for leaking zero-days without informing Microsoft beforehand. The researcher has so far released six zero-days, three of which were quickly confirmed to be exploited by attackers in the wild. As regards their motivation for launching this attack on Microsoft, Nightmare Eclipse previously alluded to being stabbed in the back and being left homeless after an agreement that was not honored – all very vague. After the sixth zero-day, Microsoft vaguely threatened the researcher with its Digital Crimes Unit, which works closely with law enforcement, before quickly backing down after an outpouring of negative responses. The Register approached Microsoft for more information. ®

Ebola is terug. En de bestrijding van dit dodelijke virus staat of valt met het op tijd opsporen van besmettingen.

Groene waterstof is cruciaal voor de energietransitie, maar een Nederlandse markt ervoor komt nauwelijks nog van de grond. Potentiële producenten, klanten en transporteurs kijken naar elkaar. In Rotterdam wordt die patstelling langzaam doorbroken. „Als het waterstofnetwerk er eenmaal ligt, zal er vanzelf een markt ontstaan.”

Een 21-jarige man die zwaargewond raakte bij een steekpartij aan de Nijhoffstraat in Zwijndrecht is aan zijn verwondingen overleden in het ziekenhuis. Dat meldt de politie woensdag. Het gaat om een inwoner van Zwijndrecht.

Hahahahahaha wat. We zijn nog maar net bekomen van het wereldschokkende nieuws dat Esmah Lahlah (nadat ze in aanloop naar de Tweede Kamerverkiezingen als nummer 2 van de GL-PvdA-lijst 2x voor een burgemeestersfunctie werd afgewezen en een maand geleden nog stelde dat ze "voorlopig" Kamerlid bleef) VERTROK uit de Tweede Kamer om wethouder te worden in de voor haar nog onbekende stad Amsterdam, vandaag stond ze alweer met haar blije kopvod en "met een opvallend grote Palestijnse vlag op haar telefoonhoesje" op de presentatie van het Amsterdamse coalitieakkoord. Wat er in dat coalitieakkoord staat? Haha nou wat denk je? Allemaal LINKSE REGELTJES natuurlijk (of zo). Veel interessanter was de duiding van PRO-Amsterdam-leider Zita Pels (bekend van haar gooi naar het Amerikaanse presidentschap en succesproject Stek Oost) over haar uit Den Haag ingevlogen surprise-act die ineens over het onderwijs in de hoofdstad gaat. Wat blijkt: Zita Pels heeft alle vertrouwen in Esmah Lahlah, net als Jesse Klaver dat had, zoveel vertrouwen dat Zita Pels NIET KAN GARANDEREN dat Esmah Lahlah nu wél haar termijn uitzit. Zita Pels antwoordt op de vragen over Lahlah als volgt: "In Amsterdam zijn we vies van dit soort Haagse spelletjes. Wij hebben gewoon een fantastische wethouder hiernaartoe gehaald." Wij zijn geen expert, maar als je in het geheim alle mogelijke moeite doet om van je plek als nummer 2 van de partij af te komen, je eigen partijgenoten daarover bedondert, zegt dat je niet van plan bent om te vertrekken, je partijleider laat liegen dat je niet zal vertrekken en dan bij de eerste de beste mogelijkheid alsnog vertrekt, dan is er toch sprake van een Haagse soap met wat ons betreft een aardig hoog spelletjesgehalte. Maar zulke gedachten zijn volgens Zita Pels allemaal stom en gemeen.  "Alles wat die rechtse partijen in Den Haag maar lopen uit te kramen over hoe het allemaal beter zou moeten, maar het niet voor elkaar krijgen, doen wij hier wél. (...) Dat het dan weer over poppetjes, garanties en dat soort dingen gaat… Ik vraag mij af of dat óóit over één VVD’er is gevraagd." Ahaaa, gewoon weer een COMPLOT VAN RECHTS dus. Het zijn poppetjes, en dat Zita's poppetje dan toevallig een poppetje is dat ergens anders zat omdat daar 100.000 mensen op hadden gestemd voor de komende 4 jaar, daar moeten we maar niet zo moeilijk over doen. Het is wel Amsterdam hè, niet een of ander lullig provinciestadje. Duidelijk.

The moderators of the biohacking subreddit say that peptide and hormone replacement therapy companies have been surreptitiously spamming Reddit in an attempt to get their posts scraped by AI chatbots. The strategy is an effort to systematically manipulate the answers provided by chatbots by manipulating the underlying source material that those chatbots will scrape—in this case, a popular Reddit community. 

In a post last week, the moderators of r/biohackers said they would be banning new posts about peptides and hormone replacement therapy (HRT) because of attempted manipulation by the companies that make, market, and sell them. r/Biohackers is a long-running subreddit about using supplements, experimental pharmacology, and other longevity or fitness-adjacent themes; peptides and HRT have become a wildly popular topic of discussion on the subreddit, especially as companies try to market them off-label or as grey-market compounds. 

“As AI search engines increasingly pull answers from Reddit, companies are using us for AEO. On top of that, there's been an explosion of peptide interest and AI usage flooding the sub. Together, this has put serious pressure on content quality,” a post by the moderators read.