TheGeeks.Net Logo

26 years, 11 months, and 17 days of TheGeeks.Net and still going strong!

Slashdot (Last Update: 2026-11-13 23:00:00GMT)

Lego's BrickLink Marketplace Back Online After Week-Long Outage Caused By 'Cyber Incident'

LEGO's BrickLink marketplace is back online after a week-long outage caused by what the company described as a "cyber incident," during which an unauthorized third party accessed some user data. Details about exactly what data was accessed remain unclear. The site went offline on November 5 and remained unavailable until November 12, preventing users from buying or selling LEGO sets and parts during the busy holiday shopping season. According to Brick Fanatics, LEGO initially described the outage as "necessary work" before confirming that the platform had suffered a security incident. In an email to users, LEGO acknowledged that "some of the information associated with your account was accessed and disclosed by an unauthorized party," including potentially usernames and IP addresses. However, the company insisted that "your password, postal address, and financial information were not disclosed." Those assurances have since come under scrutiny following reports of convincing phishing emails containing detailed personal and purchase information. The outage also dealt a significant blow to independent sellers who rely on BrickLink for income. Simon Webster, who operates stores on both BrickLink and rival marketplace Brick Owl, reported that his overall sales revenue fell 52% over a four-day period, even as sales through Brick Owl rose 79%. "Their comms are amateur at the best of times, but surely they should be able to send an email to let sellers and buyers alike know what is happening and what they're doing to rectify it," Webster said. "But no, we're all left in the dark." The incident has renewed concerns about BrickLink's aging infrastructure. Founded in 2000 and acquired by LEGO in 2019, the marketplace reportedly runs on a complex collection of interconnected systems that makes modernization difficult. The Brick Fanatics report questions whether the 25-year-old platform remains fit for purpose and whether prolonged outages and security concerns could push sellers toward competing marketplaces like Brick Owl.

Read more of this story at Slashdot.

US Seizes $1.2 Billion In Crypto Stolen From Binance

U.S. authorities have seized or restrained more than $1.2 billion in cryptocurrency stolen during Binance's $6 billion October hack, which the FBI attributes to North Korean military-linked hackers known as "TraderTraitor." The DOJ also said it disrupted infrastructure behind the "FaceStealer" deepfake scam, blamed for stealing more than $400 million in cryptocurrency. CNBC reports: Collective efforts between the U.S. government and private sector have resulted in more than $2.7 billion of that amount being frozen. [...] The DOJ said it was taking coordinated action against what it called the North Korean government's "schemes to fund its regime through the massive theft of cryptocurrency." That includes "the court-authorized seizure and restraint of more than $1.2 billion worth of cryptocurrency recently stolen from Binance," it said. DOJ units, law enforcement partners and virtual asset service providers have been working to intercept the stolen assets. But efforts to track and freeze the assets are ongoing, as TraderTraitor actors continue to launder them through various cryptocurrency channels. Authorities have also seized cloud-based infrastructure used in a massive identity impersonation scam known as "FaceStealer," which has seen more than $400 million worth of cryptocurrency stolen over 18 months, the DOJ said. The scheme sees hackers set up fake video meetings using stolen accounts and recordings of people known to the target by using AI-generated deepfakes. The hackers then say a technical problem requires a fix, install malware on a computer and take over the victim's communications, steal their cryptocurrency and target their contacts -- sometimes months or more than a year after the initial compromise.

Read more of this story at Slashdot.

Mozilla to Shut Down Solo, Deleting Users' Websites and Data

Mozilla is shutting down Solo, its AI-powered website builder and hosting service, on November 30. A notice on the Soloist.ai homepage reads: "We've made the difficult decision to close Solo. We have appreciated all of your support building and growing this product, and the feedback we've received from all of you. Solo will cease operations on Nov 30, 2026." The Register reports: Mozilla launched Solo in December 2023 as a "Mozilla Innovation Project," aimed at helping sole traders to build themselves a webpage for their services. Some 54,000 people used its LLM to build pages, and relied on Mozilla to host them -- complete with custom domain names. Users now have just over two weeks left to find a new home for their pages, although Mozilla says it first notified them on October 1. According to the support FAQ, users can download a ZIP containing an HTML export, contact form and newsletter submissions, and a CSV linking to their images. The images themselves must be downloaded separately. Domains purchased through Solo Domains must also be moved to Name.com, with Mozilla handling the transfer after users create an account and supply its code.

Read more of this story at Slashdot.

Microsoft's Global Outage May Be Worse Than Amazon's Or Crowdstrike's, Expert Says

An anonymous reader quotes a report from Ars Technica: A global outage taking down a wide range of Microsoft 365 services remains ongoing Friday morning. The outage started midday Thursday, impacting users of Microsoft email, cloud, and AI services. Microsoft has documented the full list of services impacted by the error, while moving early Friday morning to protect customers around the world from losing emails during the extended disruptions. "Recovery actions are ongoing," the Microsoft 365 Status account confirmed on X. "To help preserve delayed mail during this event, we've extended email timeout to 48 hours." Similar to recent world-shaking outages of widely used tech like Amazon Web Services and CrowdStrike, the Microsoft disruption looks like "one of the biggest outages of all time," Ciaran Martin, the former head of the UK's National Cyber Security Centre, told NBC News. Possibly even "worse," he suggested. Businesses, hospitals, police departments, and schools were among those scrambling to work around the outage. In Japan, it disrupted government IT infrastructure, according to deputy chief cabinet secretary Masanao Ozaki. NBC's report documented various harms, noting that "few public bodies were immune from the outage." In some cases, doctors couldn't send patients "important" updates on medication changes or follow-up care. The financial sector suffered, too, with people blocked from making bank transfers since they couldn't receive verification codes. Justice systems were also hobbled. The Supreme Court in the Philippines saw its legal work derailed, NBC reported. And one US sheriff's office in Colorado reported that the outage made it difficult for people to post bond for prisoners' immediate release. It's unclear how many users were affected, but Microsoft estimated in January that the total number of paid Microsoft 365 commercial subscriptions exceeded 450 million. Microsoft's most recent updates confirmed that it's seeing "broader improvements in North America, sustained improvements across much of Europe, and encouraging recovery signals in Asia Pacific." "Some users may still experience intermittent access issues or delayed email delivery as mitigation continues across remaining affected infrastructure," Microsoft said. "Our focus remains on stabilizing recovered infrastructure, completing mitigation in remaining impacted areas, and reducing delayed email queues and backlogs while we validate service consistency across connection methods."

Read more of this story at Slashdot.

ChatGPT's New Wallet Lets AI Agents Shop For You

OpenAI has launched ChatGPT Wallet, a feature that lets its Dots AI agents help users choose products and complete purchases on their behalf. TechCrunch reports: The option will initially be available to a limited number of U.S. ChatGPT Pro subscribers, ages 18 and up, with a U.S.-issued Visa, Mastercard, or American Express. OpenAI says that users are fully in control of the purchases, as they're able to review the items, the total, and the payment card that will be used to complete the transaction before the checkout occurs. In addition, users will approve the purchases directly with a security check like Face ID or a fingerprint, which creates a record of their transaction. [...] The company notes that customers who shop via their dots will still be able to earn their credit card rewards and be able to take advantage of protections that typically come with cards, like being able to dispute transactions.

Read more of this story at Slashdot.

Advocacy Groups Sue AI Giants to Freeze New Models, Warning of 'Catastrophic' Risks

A coalition of online safety and consumer advocacy groups has sued five of the world's leading artificial intelligence companies, asking a California judge to halt the development and deployment of new AI models until the companies can address what the plaintiffs describe as potentially "catastrophic" risks. The lawsuit alleges the companies are violating California unfair competition law by endangering public health and computer systems, arguing that increasingly autonomous AI could ultimately escape human control. The Associated Press reports: The filing, first reported on by The Associated Press, asks a judge to stop Anthropic, Google, Meta, OpenAI and SpaceXSI from developing or deploying new AI models, pointing to documented examples of cyberattacks and other harmful actions by AI systems and the companies' own alarming acknowledgments that their technology has the potential to someday destroy humanity. "No other industry is allowed to treat its own development of unsafe products -- much less ones that could kill us all -- as inevitable," reads the complaint from the Irreplaceable Education Fund, Public Citizen, Heat Initiative and the Alliance for Secure AI. "Plaintiffs bring this suit to stop Defendants from continuing their unlawful path to disaster." [...] The plaintiffs, all nonprofits, allege that the companies named in the lawsuit have violated a California unfair competition law by endangering public health and interfering with the use of property such as computer systems. They claim they've had to divert resources away from other planned work to address the acute harms threatened by each of the companies' advancing AI models. They also warn that the companies' goals of creating AI systems that are broadly as smart as humans and can increasingly manage tasks and learn things autonomously could result in a permanent loss of control of the technology and heighten existential risks to humanity.

Read more of this story at Slashdot.

Nvidia Employees Petition For Jensen Huang's Return

An anonymous reader quotes a report from Wired: Some Nvidia employees are calling for Jensen Huang's return even after his multiple reported extramarital affairs and abrupt resignation, according to internal correspondence reviewed by WIRED. An internal "suggestion box" post submitted before Huang's resignation by a longtime engineer at Nvidia urged the company's board to take employee sentiment into consideration prior to taking any action. The submission has attracted more than 1,600 comments since then, with several asking board members to find a way to bring back Huang. "If you believe in the mission, bring back THE boss," wrote one anonymous commenter. "We are all humans and can make mistakes. Jensen did so many good things and he needs a second chance," wrote another. One employee went as far as sending a companywide email demanding transparency into Huang's exit. "I stand by Jensen," the staffer wrote. "Not because I believe any person is infallible, but because I refuse to believe that standing for fairness must mean standing at a distance from someone whose leadership has meant so much to us." [...] It's been business as usual inside the company throughout this week, but Huang's resignation left many employees stunned. In the hours after, about two dozen employees posted on LinkedIn in support of Huang, with one describing their faith in his leadership as unwavering. Over the same period, WIRED couldn't identify any posts from Nvidia employees in support of his resignation. One employee who has been at Nvidia for a couple of years and wasn't authorized to speak publicly says they perceive the desire for Huang's reinstatement as widespread. They worry the company will eventually suffer without its founder at the helm and say that the board must bring him back. "Nvidia is Nvidia because of Jensen," the employee tells WIRED. Many employees had expected a board investigation to conclude before any big changes would occur. For instance, the suggestion-box post called on the board to share its findings with employees and formally solicit their sentiment "about Jensen's continuing as our CEO." Instead, Huang left just as the inquiry had begun. Staffers are seeking to better understand why. "If America fails the man who helped build its future," the employee in the companywide email stated, "then this world does not deserve Jensen Huang."

Read more of this story at Slashdot.

Parents and Teachers Decry Google Pledge To Yank Search If Schools Block AI

An anonymous reader quotes a report from The Guardian: Parents and teachers across the US are criticizing Google's announcement that schools choosing to block AI tools could also lose access to Google Search. Google announced last week a range of new AI tools for schools and classrooms, alongside options allowing teachers and administrators to restrict their use. The company said schools should have control over whether students use AI in the classroom, but that schools that choose to block Google's AI tools will also lose access to its search engine. [...] Parents and teachers across the country raised concerns to the Guardian about AI's potential to weaken students' critical-thinking skills and the growing influence of big tech in education. Some called on schools to consider alternative search engines, while others argued that students should be taught how to use AI responsibly rather than prevented from accessing it altogether. Jen Atay, a 51-year-old teacher in Hawaii, lambasted Google's approach, saying: "When the software is free, you are the product, and it is inappropriate for Google to test or develop AI with minors. This should not be allowed at all." A 44-year-old father of two boys in Amissville, Virginia, said he worries that "AI will weaken people's ability to think critically. I use AI in my work, but it would not be effective if I did not have well over a decade of experience under my belt. Even the best models are often flat-out wrong in their responses." [...] Others questioned why schools should depend on Google at all. An 84-year-old retiree and mother in Maryland, said: "Google decided to follow the evil path to riches. When they started, they were great. Today they are simply evil money grubbers Schools should tell Google to go pound sand and simply have kids use DuckDuckGo or one of the other search engines There is nothing Google offers that is not available from some other source." [...] Not everyone believes blocking AI is the answer. Some argued that schools should focus on teaching students how to use the technology responsibly. A 67-year-old emerging technology teacher in Texas said: "I do not blame Google. AI is not going away. I've been very frustrated this year trying to teach AI literacy with AI blocked. Schools need to teach how to properly use AI, not block it." A California resident echoed that view, arguing that schools could use Google's AI tools to teach students to question the information they receive. "Google Search has existed since the 90s and it's crazy of them to completely remove it instead of just removing Gemini. That being said, I would like to see schools actually permit the use of Gemini and use it as an opportunity to show students how its sources aren't always valid and you can't trust everything an AI tells you," they said.

Read more of this story at Slashdot.

Phoronix (Last Update: 2026-11-13 21:07:09GMT)

AMD openSIL Achieves Its Production Goal With 6th Gen EPYC "Venice"

Since 2023 I and many open-source advocates have been very eager for AMD's openSIL project for delivering open-source CPU silicon initialization as a replacement to the traditional AGESA code. With Zen 5 there was proof-of-concept support that we have enjoyed with Coreboot on an MSI Ryzen motherboard and a Gigabyte EPYC server motherboard thanks to the Coreboot-based Dasharo ports by 3mdeb. The goal for production readiness was for Zen 6, but with this week's EPYC 9006 SP7 announcement the openSIL topic wasn't touched on. So I asked around...

XRAID Publicly Released As New RAID Implementation For XFS

Longtime Linux developer Christoph Hellwig today announced the initial public release of XRAID. XRAID is a declustered parity RAID implementation integrated into the XFS file-system. XRAID is focused on RAID for zoned XFS deployments...

Linux 7.5 To Upstream Driver For New Glanda GPU

Sent out today was the drm-misc-next pull request for the week of new material to queue in DRM-Next until the Linux 7.5 merge window gets underway in late December. Most notable this week is the introduction of the new GlandaGPU driver...

Undeadly.org (Last Update: 2026-11-11 18:58:28GMT)

LibreSSL 4.3.5 and 4.4.1 released

The world moves on, and with it comes bugfixes and new releases. The LibresSSL project has announced the release of versions 4.3.5 and 4.4.1, in an announcement that reads,

List:       openbsd-announce
Subject:    LibreSSL 4.3.5 and 4.4.1 released
From:       Brent Cook <busterb () gmail ! com>
Date:       2026-11-11 13:37:27
Message-ID: avRvlxkd6oW6QuJ2 () bobcat ! local

We have released LibreSSL 4.3.5 and 4.4.1, which will be arriving in the
LibreSSL directory of your local OpenBSD mirror soon.

Read more…

OpenBSD top(1) adds flag to show chroot, pledge and unveil status

With one recent commit, the top(1) command on OpenBSD became quite a bit more useful. The commit adds a new -Q flag to show each process' use of the chroot(2), pledge(2) and unveil(2) facilities.

The commit message reads,

List:       openbsd-cvs
Subject:    CVS: cvs.openbsd.org: src
From:       Klemens Nanni <kn () cvs ! openbsd ! org>
Date:       2026-11-05 17:54:16

CVSROOT:	/cvs
Module name:	src
Changes by:	kn@cvs.openbsd.org	2026/11/05 11:54:16

Modified files:
	usr.bin/top    : display.c machine.c machine.h top.1 top.c 

Log message:
add Q flag/key to show pledge/chroot/unveil usage

Read more…

OpenSSH 10.6p2 released

In an announcement posted on social media, Damien Miller (djm@) writes,
OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability.

If you operate a Linux system that uses musl libc without PAM (Alpine Linux is one example) then stop reading and set PasswordAuthentication=no or disable SSH for these systems IMMEDIATELY.

This vulnerability does not exist on non-Linux systems, Linux/glibc systems and Linux systems that use PAM for password authentication.

We consider the root cause of this bug to be outside OpenSSH itself, but we're in a good position to deliver a mitigation quickly.

Read more…

Work on GEFS (the Good Enough File System) for OpenBSD progresses

As previously reported, Ori Bernstein is working on GEFS, the "Good Enough File System" imported to OpenBSD, and his EuroBSDCon 2026 presentation was very well received. In fact, the video is among the most frequently played from the conference.

Now Ori has followed up with more evolved code that includes several important steps towards makin the new file system fit for general use. In a message to tech@, Ori writes:

List:       openbsd-tech
Subject:    Re: GEFS on OpenBSD: A very early preview
From:       ori () eigenstate ! org
Date:       2026-10-31 17:08:42

So, it's probably time for a few updates. First
off, thanks to Martijn, and everyone else who
tried it out and sent patches.

Everything is updated and rebased, and the diff
has been regenerated with all of the lastest.

Read more…

emulators/wine (re)entering OpenBSD ports

In his message to the ports@ mailing list, Thomas Frohwein (thfr@) leads in,
In what might the most surprising port proposal of the year, I'm proud
to present a new port for wine.

talking not about the beverage, but the Windows Emulator that enables running binaries for that operating system on other systems.

Among the editors there is no one with enough recent Windows exposure to comment seriously on this, but we do vaguely remember that a port of this software existed back in the day.

So if this falls within the things you are interested in or actually need, we would encourage you to read the entire emulators/wine thread and the later supplement on new port: emulators/wine-extras: scripts for winetricks and wine-steam to keep up to date on developments.

Then, if you are able, please help the effort by testing the ports and reporting back.

dbupdate(8) added to -current

Theo de Raadt (deraadt@) has committed to -current a (WIP) new utility for updating system databases:

CVSROOT:	/cvs
Module name:	src
Changes by:	deraadt@cvs.openbsd.org	2026/10/20 19:08:58

Added files:
	usr.sbin/dbupdate: Makefile dbupdate.8 dbupdate.sh 

Log message:
initial draft of dbupdate(8) for updating (signed) zoneinfo and cert.pem
from a new cdn.openbsd.org/pub/OpenBSD/dbupdates/ directory.  We can't
do this nicely with syspatch(8) because it requires patches in sequence
so a new tool had to be written.  It is intentionally kept very simple
so that it can be studied because we intend to run this in root cron,
(the non-simple parts figure out quickly when not to update).
looked at by sthen beck lucas dgl

Read more…

OpenBSD 8.0 Released

The OpenBSD project has announced OpenBSD 8.0, its 61st release.

The new release contains a number of significant improvements, including but certainly not limited to:

  • OpenBSD/amd64 kernel virtual address space is now 512GB [See earlier report]
  • Mitigation for AMD Zen-2 operation cache corruption added [See commit]
  • OpenBSD now uses AES instructions (on amd64 and arm64 when available) to increase speed of swap encryption/decryption [See commit]
  • The OpenBSD/loongson hardware platform has been retired [See earlier report]
  • getexecpath(3) added [See commit]
  • drm(4) has been updated to Linux 6.18.53
  • vmm(4)/vmd(8) improvements:
    • files are now used to manage VM ownership [See earlier report]
    • multi-processor VMs are now supported [See earlier report]
  • WPA3 support introduced [See earlier report]
  • syslogd(8) privileged and non-privileged parts now separate binaries [See earlier report]
  • qwz(4) driver for Qualcomm Technologies WCN7850 wireless network devices added [See commit]
  • PF queues break the 4 Gbps barrier [See earlier report]
  • httpd(8) and smtpd(8) are now randomly relinked at boot [See earlier report]
  • httpd(8) has seen many improvements:
    • support for custom HTTP headers [See earlier reports]
    • header block/drop rules for request filtering [See earlier report]
    • improved default crypto methods for HTTPS [See earlier report]
    • cache control for static files [See commit]
  • relayd(8) has received several improvements:
    • improved default crypto methods for HTTPS [See earlier report]
    • support for ECDSA keys and certificates was added [See earlier report]
    • filter rules gained support for Lua patterns(7) [See earlier report]
    • support for multiple resolvable addresses [See commit]
  • rtrd(8), a RTR-To-Router protocol daemon, and its control program, rtrctl(8), were imported [See earlier report]
  • acme-client(1) gained support for external account binding [See commit]
  • Several improvements in OpenBGPD [See earlier reports]
  • A number of incremental improvements in rpki-client(8) [See earlier reports]
  • tmux(1) gained support for floating panes [See commit]
  • LibreSSL 4.4.0 [See earlier reports]
  • OpenSSH 10.6 [See earlier reports]
  • llvm/clang(1)/lld(1) updated to version 22.1.6 [See earlier report]
  • LLVM toolchain added to OpenBSD/sparc64 [See earlier report]
  • compiler-rt, libunwind, libcxxabi, libcxx updated to version 22.1.8

In addition, this release offers a number of bug fixes and as well as numerous improvements in hardware support.

See the full changelog for more details of the changes made over this latest six month development cycle.

The Installation Guide details how to get the system up and running with a fresh install, while those who already run earlier releases should follow the Upgrade Guide, in most cases using sysupgrade(8).

Readers are encouraged to celebrate the new release by donating to the project to support further development of our favourite OS!

Schneier (Last Update: 2026-11-13 22:00:46GMT)

AI Doesn’t Have to Go Rogue to Break the World

This essay is adapted from a keynote speech delivered at the DEF CON 34 conference in Las Vegas on August 7, 2026. The essay originally appeared in CyberScoop.

I want to talk about AI hacking. There are three aspects: people hacking AI systems, people using AI to hack other systems, and AIs hacking systems on their own, not even maliciously. The last two matter more than the first. The third is the weirdest and potentially the most destabilizing.

I started writing about this in 2021 and in my 2022 book, A Hacker’s Mind. Back then I said it was mostly still science fiction, but not stupid science fiction. We’re seeing it more and more, especially in the past year. The trends I’m describing don’t require a major breakthrough in AI. They’re starting to happen now, and they’ll happen more often as AIs get better at autonomous problem-solving. And it will involve far more than computer code.

AI will hack all sorts of social, economic and political systems. It will find vulnerabilities and exploit them. This is a difference in kind, not just degree. We’re not ready for it, and we need to think about the implications now.

First, I want to broaden the term “hacking.”

The tax code isn’t computer code, but it is code. It’s a series of algorithms with inputs and outputs. It has vulnerabilities, which we call loopholes, and exploits, which we call tax avoidance strategies. Black hat hackers exploit them for profit. We call them accountants and attorneys.

What is a hack? One definition: “Something that a system permits, but is unanticipated and unwanted by the designers.” It’s subjective and implies novelty and cleverness. A hack follows the rules of a system but subverts its goals or intent, just as a software hack follows the logic of code while doing something its authors neither anticipated nor wanted.

All systems of rules can be hacked, including professional sports, customer reward programs, financial systems and politics. Hacks even work against our cognitive functions. A curved hockey stick is a hack, and we know the name of the man who invented it. Mileage runs were a hack. The filibuster was originally a hack in Roman times. Gerrymandering is a hack. Hedge funds and private equity are full of them.

A system is just a set of rules or norms, and the rules aren’t always formal. Even the best-designed rules will be incomplete, inconsistent or ambiguous. As long as people want to subvert a system’s goals, there will be hacks.

AIs are becoming hackers. After decades of slow progress, they’ve gotten very good at finding and exploiting vulnerabilities in computer code. They do this largely autonomously, and they’re getting better scarily fast. But the implications extend far beyond software, to the tax code, financial regulations and all sorts of social, economic and political systems.

There are two distinct issues. First, someone might instruct an AI to hack one of these systems, feeding it the world’s tax codes or financial regulations to find profitable loopholes. Second, an AI might hack a system on its own, inadvertently. Both are dangerous, but the second is worse because we might never know it happened.

Now, reward hacking. AIs don’t solve problems the way people do. They stumble on solutions we never anticipated, and some subvert the intent of the system. They don’t share our context and don’t necessarily understand the implications, norms and values we take for granted.

Reward hacking is when an AI achieves a goal in a way its designers neither wanted nor intended.

Early pre-LLM examples are telling. In a two-person soccer simulation, an AI learned that kicking the ball out of bounds forced the opposing goalie to throw it in and leave the goal undefended. In a stacking simulation, an AI learned to flip a block upside down rather than stack it. In an evolution simulation where the goal was to cross a distant finish line, an AI made itself tall enough to fall over the line instead of growing longer legs or stronger muscles.

These are all hacks, the result of poorly specified goals or rewards. Today, they’d come from bad prompting.

The problem is universal. One researcher tried to teach a robot vacuum not to bump into things. Instead, it learned to drive backward, because there were no sensors in the back.

Any capable AI will find hacks wherever the rules have problems, inconsistencies or loopholes that still produce an acceptable solution. We see a hack because we understand context. The AI doesn’t, at least not in the same way.

This problem shows up often in myth.

In the story of King Midas, the god Dionysus grants him a wish: everything he touches turns to gold. Midas ends up starving when his food, drink and daughter all turn to gold. It’s a specification problem. He programmed the wrong goal.

In the Golem of Prague, a ghetto animates a clay statue to guard its residents. It guards them past all reason until they figure out how to turn it off. This is a guardrail problem. The villagers never limited the golem’s actions.

More generally, think of this as the genie problem. Genies are precise about the wording of wishes and can be maliciously pedantic when granting them. There’s no way to outsmart a genie. Whatever you wish for, he can grant it in a way you wish he hadn’t.

The reason is that in human language and thought, goals are always underspecified. We never include every caveat, exception and proviso, and we never close off every avenue for hacking. Any goal we specify will be incomplete. That’s largely fine in human interactions, because people understand context and usually act in good faith.

If I asked you to get me coffee, you’d pour a cup from the nearest coffee pot or walk to the corner shop. You wouldn’t bring me a pound of raw beans, buy a coffee plantation or snatch a cup from a stranger’s hands. I wouldn’t have to specify any of that. You’d just know.

Similarly, if I asked you to develop a technology that turns things to gold on touch, you wouldn’t build it to starve the person using it. You’d just know.

In 2015, Volkswagen was caught cheating on emissions tests. Human engineers programmed a regular computer to detect testing and behave differently during it. The cheat went undetected for years because it’s hard to tell what software is doing.

If I asked you to design engine control software that maximizes performance while passing emissions tests, you wouldn’t design it to cheat without realizing you were cheating. An AI would, because it will think “outside the box” when it has no concept of the box.

Unless programmers specify that the system must not behave differently during testing, an AI might come up with the same hack. The programmers would be satisfied, the accountants would be ecstatic, and no one would know until someone audited the code.

We can now constrain the goal to avoid that particular hack, but programmers won’t anticipate others. The lesson of the genie is that there will always be hacks programmers don’t anticipate.

We’re building AI genies: systems that take broad instructions and figure out how to carry them out, sometimes in ways we didn’t expect or intend. That’s the whole point of vibe coding. You underspecify what you want and let the AI work it out. Sometimes that produces genie behavior.

We can’t completely specify goals to an AI, and AIs can’t fully understand context. More precisely, current AIs have a shallow grasp of concepts. If we asked a current LLM to get me coffee, it would almost certainly do the right thing.

I worry about goals that aren’t well represented in training data, and about hacks that aren’t obvious, whose effects are subtle, like the Volkswagen hack.

Recommendation engines are an early example. They push people toward extreme content. No one programmed that. It emerged because that’s what people respond to. It didn’t take a bad actor. A basic automated system with feedback found the hack on its own.

We’re now seeing a second generation with today’s AI coding systems. AI researcher Simon Willison asked Fable to track down a stray scrollbar in a web app. When he returned, it had opened browsers, written its own screenshot tools, edited the framework’s internal templates to make the bug appear on cue and set up a local web server to collect measurements. It found the bug, but it also did many things he never asked for. Another researcher gave Fable a complex task, and it tried to hack its own memory limits because it needed more storage.

A new OpenAI model did something similar when it hacked into Hugging Face. It was being benchmarked on its ability to turn vulnerabilities into exploits. It decided the best way to reach its goal was to break out of its containment, access the internet and break into the Hugging Face network, because it thought the answers would be there.

Today’s LLMs are acting like genies, especially when powerful models are combined with sophisticated harnesses.

There are two kinds of genies. The Dionysus genie does the wrong thing. It understands your prompt literally but not correctly, and returns a mess you never intended. The Golem genie does the right thing but tramples everything in its path to get there. The paperclip maximizer is a Golem genie.

Consider some examples. Ask an AI to deal with spam calls, and a Dionysus genie might change your phone number. Ask it to book a particular flight, and a Golem genie might hack the airline database because the flight is full. Ask it to get a refund for an online purchase, and a Dionysus genie might draft a legal threat on fake letterhead and send it to the company. Ask it to buy tickets to a popular concert, and a Golem genie might discover the ticketing system is rate-limited and spin up thousands of cloud servers to hammer it. You’d know if some of these things happened, but you might never realize if others did. More detailed prompting won’t fix this. The lesson of the genie is that no amount of detail is good enough.

AI researchers aren’t surprised by any of this. Many are working on defenses against reward hacking and subtler forms of genie behavior. Some of this falls under “value alignment”: How do we teach AIs context? And how an AI satisfies a goal matters as much as whether it does. I want to build a benchmark to measure genie-like behavior, so we know where models stand and whether alignment is improving.

Think beyond LLMs and computer code. Consider specialized AIs built to find loopholes, and hacks of more general systems: the tax code, financial regulations and democratic procedures.

Financial systems are the most likely first target, because their rules are designed to be algorithmically tractable. High-frequency trading is itself a hack. Imagine giving an AI all of the world’s financial laws, plus all the news and financial data, and the goal of finding profitable loopholes. I suspect large investment banks are already doing this. The results will be novel tricks that are legal but unintended and unwanted, some of which might break the financial system.

Tax loopholes are the next likely target, for the same reasons. For a while, AIs will identify potential loopholes, and human hackers, namely attorneys and accountants, will decide which are feasible.

Further out, expect hacks of regulatory, legislative and procedural systems, and of the broader economy.

Hacking is as old as humanity. We’re creative problem solvers and loophole exploiters. We manipulate systems to serve our interests and strive for more influence, power and wealth.

Still, no human pursues their interests without constraint. Even sociopaths are limited by the complexity of society and their own contradictory impulses. They worry about their reputation and punishment, and they have limited time. These human qualities have limited hacking.

Hacking changed as everything became computerized. Computers are uniquely hackable because of their formalism and complexity. Today, nearly everything is a computer, from cars and appliances to phones. Our social, economic and political systems, including taxation, finance and elections, all involve computers.

Until recently, hacking was exclusively a human activity. Finding a novel hack required expertise, creativity, time and luck.

AI hacking will change everything again. AIs aren’t bound by the constraints that limit people. They’ll think like aliens, and they’ll change hacking’s speed, scale, scope and sophistication, sometimes at our direction and sometimes on their own.

Speed is the easiest to see. A creative process that takes a human months or years could be compressed into hours or seconds.

Scale is next. Once AI systems start discovering hacks, they can exploit them at a scale we’re not ready for. We already see this with AI-generated slop, which is rampant on social media. AI bots post around the clock, sometimes overwhelming real human discussion. It’s hard to know how much of social media is still people talking to people. What looks like boisterous political debate may be bots arguing with other bots, artificially shaping what we think and what we think others think.

Scope makes hacks more dangerous. AIs already make decisions that affect our lives, decisions we once thought belonged only to humans. As AI systems grow more capable, society will hand them more decisions, and more important ones. Hacks of these systems will do more damage.

Finally, AI hackers are more sophisticated. They can hold more variables in working memory and generate more complex hacks. What might happen if you fed an AI the entire U.S. tax code? Would it figure out, without being told, that it’s smart to incorporate in Delaware and register a ship in Panama? Consider the Double Dutch Irish Sandwich, the strategy Apple and Google used to avoid paying U.S. taxes. It involves U.S., Dutch and Irish law and an offshore tax haven. How many loopholes will an AI find that we don’t already know about? Dozens? Hundreds? Thousands? We have no idea.

These hacks will largely be perpetrated by the powerful against the rest of us. AI is fundamentally a power-enhancing technology, and so is hacking. The more power you already have, the more a hack gives you. If you or I found a tax hack, we might make a few thousand dollars. If a large investment bank found one, it and its clients could make billions.

Our societal systems for dealing with hacks were built when hackers were human, and they reflect the pace of human hacking. We have no system of governance that can handle hundreds, let alone thousands, of newly discovered tax loopholes. We won’t be able to recover from an AI finding unanticipated but legal hacks of financial systems, operating at AI speed, scale, scope and sophistication. Hacking becomes a problem society can no longer manage.

Now, defense. AIs that find software vulnerabilities help defenders as well as attackers. Vulnerabilities can be patched, removing them permanently, or turned into signatures that security systems use to detect and block attacks. In theory, AI could identify and patch every automatically discoverable vulnerability before a product ships. This is rapidly becoming routine in software development. We call it vulnops. We can imagine a future where accidental software vulnerabilities are a thing of the past.

Deliberate vulnerabilities are different. There will be an arms race. AI will craft increasingly obscure back doors, and AI will find them. It becomes a contest between the speed of creation and the speed of patching, and between obfuscation and reverse engineering.

The same logic applies to broader systems. Yes, AI hackers might find hundreds of vulnerabilities in the existing tax code. But the same technology can evaluate potential loopholes in any proposed tax law or ruling. A legislator, a watchdog group or a reporter could take the text of a bill and identify every exploitable loophole before it passes. The difference is that, unlike software, knowing about a tax loophole doesn’t mean it gets patched. In theory, though, we can fix them before the rich and powerful exploit them. So maybe defense will come out ahead here, too.

That requires resilient governing structures that can respond quickly. It won’t help if updating the tax code takes years, or if a legislative hack becomes so entrenched that it can’t be fixed politically. Maybe a lobbyist put it there on purpose. Maybe it was discovered after the law passed, and now lobbyists want to keep it. Microsoft can patch the vulnerabilities it finds. Patching is much harder when legislatures have to do it. We need society’s rules and laws to be as patchable as our computers.

This is a hard problem of modern governance, and it goes well beyond AI. It’s the problem of building governing structures for the speed and complexity of the information age.

The umbrella idea is trust. What do we need for AI systems to be truly trustworthy? Capability isn’t enough.

AIs won’t be trustworthy if the companies controlling them spy on us or subtly manipulate us. I call this the friend vs. tool problem. Will we have AI agents, or AI double agents?

AIs won’t be trustworthy if they’re insecure. How do we know they haven’t been manipulated? Almost all AIs operate in adversarial environments, so someone will benefit from hacking them. Unless we know they’re secure, we shouldn’t trust their output.

And AIs won’t be trustworthy if they act like genies. We need to know they’ll perform tasks the right way, not just perform the tasks we ask for.

I’ve written extensively about the need for “integrous” AI, including how to think about the problem, what a research agenda looks like and what good laws and policies look like. I predict integrity will be the key security problem of this decade, just as confidentiality was the key problem of the last one. This applies to both AI and the internet of things.

The big shift is agency, which I think of as Web 3.0. Computers now affect the physical world directly and with growing autonomy. Sensors go from data sources to attack surfaces, and actuators go from outputs to attack capabilities. An integrity failure no longer means bad spreadsheet data. It means the wrong dosage, the wrong valve position or the wrong braking distance.

Integrity isn’t one thing. I break it into input integrity, processing integrity, storage integrity and contextual integrity. Each is complex and important, and each deserves its own talk. I’ve written about them, and I hope you’ll read it.

Much of this isn’t really an AI problem. It’s not a technical problem so much as a capitalism problem or a democracy problem.

The failures of late-stage capitalism and democracy in the information age both stem from the rich and powerful getting too good at hacking our social, economic and political systems. This is the core argument of my 2021 book.

Seen this way, AI is exacerbating existing problems. Human inefficiency has largely kept those problems in check, and that won’t work much longer.

So consider this a call to action. Technically, we need to understand how AIs hack systems, build systems that are resilient to hacking and build AIs that won’t act as genies. Politically, we need to learn to govern and regulate at the speed of technology. Otherwise, market failures will overwhelm our ability to govern them.

I said hacking is as old as humanity and that AIs will overwhelm our ability to deal with it. The solutions aren’t specific to AI, but AI makes them more urgent. We need to understand them, and we need to implement them.

Another Way Police Are Locating People from Their Smartphones

Penlink’s Webloc is an application that locates people using information from the weather, gaming, email, and religious apps on their phone. It’s sold to the police.

The tool collects vast quantities of location data from smartphones via commonly used weather, gaming, email and religious apps. It can build a detailed picture of where a smartphone has been over the past 12 months, and update the data hourly, showing the movements of people on a near real-time basis. Law enforcement officers can use Webloc to zero in on a map and look at all phones that were present at a specific place and time, analyzing “billions of location data points,” according to company documents reviewed by Bloomberg.

There’s a nice infographic that explains how the system works at the link.

Three People Arrested for AI-Enhanced Impersonation Fraud

It’s hard to believe how lucrative this crime can be:

According to a press release from the United States attorney’s office for the southern district of New York, three men ­ Jacob Soall, Sharon Hazan, and Guy Sheetrit ­ were arrested for using AI to alter and impersonate the voices and images of executives and attorneys at various companies in order to convince employees to send over large payments. Soall and Hazan were arrested in Spain over the summer, while Sheetrit was arrested in the United Kingdom in September. The alleged fraud took place between 2024 and 2026.

With the help of AI, the men allegedly acted as a corporate executive, targeting employees of various companies and telling them they needed their help with sensitive financial transactions. They would then instruct the employees to get in touch with lawyers at a large international law firm. The men would then impersonate a lawyer at these firms and have the employees wire a large amount of money.

The men ultimately stole more than $129m from companies all over the world including in the US, according to the DoJ.

Always remember that there are three parts of AI security: security of AI, security with AI, and security from AI. This is the third.

New OpenSSH Vulnerability

It’s a bad one, and it’s been in the code for a decade:

A newly disclosed flaw involving OpenSSH and musl, dubbed “*sshole,” allows attackers to log in to certain Alpine Linux and other musl-based Linux accounts configured to block password authentication simply by entering an oversized password.

“Oversized” means longer than 256 bytes. Details.

Slashdot thread. And another news article.

AI Security

Two weeks ago, I attended the [un]prompted AI security conference in San Francisco. It was an excellent event: three days of very dense talks about all aspects of AI security. (My talk was about integrous AI, and I will post it when it is online.)

AI security can be divided into three broad topics. It’s important for researchers to understand which one they are working on. And it’s important for us as a community to work on them all. They are: security of AI, security with AI, and security from AI. [un]prompted had good talks about all three.

Friday Squid Blogging: New Jurassic Squid Predecessors

News story: “Scientists discover a bizarre Jurassic ‘squid’ unlike anything ever seen.”

Scientists have identified the “fattest” belemnite ever discovered, a bizarre, barrel-shaped squid relative that lived in Wyoming’s ancient seas 160 million years ago. The exceptionally rare fossils reveal a creature unlike anything previously known, potentially a predator of smaller squid-like animals and a surprising survivor of a supposedly vanished family.

As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.

Blog moderation policy.

Pinpointing Location of Videos from Background Airplane Sounds

This is fascinating:

The video describes a technique that can reveal where an otherwise unidentifiable recording was made by analyzing its audio for the faint sounds of passing aircraft. The technique is both fascinating and frightening.

It works by looking at Doppler curves, which plot the way a plane’s sound changes as it passes overhead because of the Doppler effect. This is the same familiar Doppler effect that causes the frequency of a siren to rise as it approaches and then fall as it passes by and moves away. More generally, it’s the phenomenon whereby the frequency of a wave perceived by an observer changes when the observer and the source of the wave are moving in relation to one another.

[…]

It’s sound that’s relevant here, though, and specifically the sound of aeroplanes. Early in his video, Colsto brings up a map of the flights that were in the air at the time the video he’s tracing was recorded. Much of this information is publicly available. Aircraft equipped with Automatic Dependent Surveillance–Broadcast (ADS-B) transmit data about their position, velocity, and altitude, which flight-tracking services collect and make available to the public. While not every plane is tracked, the system provides an enormous amount of information about aircraft movements.

LXer (Last Update: 2026-11-13 23:24:29GMT)

Slax Linux Makes a Comeback

Slax now runs on Debian 13 with a built-in AI assistant, and it can boot with Secure Boot on compatible PCs.

Miniature industrial IoT gateway with dual Gigabit Ethernet and optional Wi-Fi 6, LTE

Compulab has detailed its IOT-GATE-IMX8PV2, a fanless industrial IoT gateway powered by NXP’s i.MX8M Plus processor. The small-form-factor system combines dual Gigabit Ethernet, optional Wi-Fi 6 and LTE connectivity, and isolated industrial I/O in a 105 × 80 × 30mm aluminum enclosure. The gateway uses a quad-core Arm Cortex-A53 processor running at up to 1.8GHz,…

Google Summer of Code mentor summit 2026

Every year, the Google Summer of Code (GSoC) Mentor Summit brings together open source maintainers, community leads, and mentors from across the globe. It is an energizing unconference where the diversity of open source can be touched. This is a unique occasion to share what works (and what doesn’t) across…