geek

25 Jul 2026

Slashdot

OpenAI's Rogue Agent Went Unnoticed For a Week

An anonymous reader quotes a report from Reuters: The OpenAI agent that broke into tech firm Hugging Face went on a dayslong hacking spree that OpenAI didn't notice until well after the threat was contained and the FBI was alerted, according to people familiar with the investigation. The agent -- a program capable of making decisions and executing complex tasks with little or no human oversight -- attempted to break out of its isolated testing environment at OpenAI around July 9, according to two of the people. The intrusion at Hugging Face, which operates as a repository for AI tools and models, began two days later on July 11 and lasted until July 13, said Thomas Wolf, Hugging Face's co-founder. It took several more days for OpenAI to realize its agent was behind the hack, and the two companies only communicated about it for the first time on or around July 20, according to Wolf and three of the people familiar with the investigation. OpenAI's public disclosure, on July 21, thatone of its agents had slipped out of control and carried out the break-in at Hugging Facedrew global attention. But many details of the hack, including how long the agent went rogue and OpenAI's belated knowledge of it, are being reported here for the first time. Hugging Face is preparing a public timeline of the hack, Wolf said, adding that he could not speak to what happened at OpenAI. In a statement, OpenAI said the hack was unprecedented and "marks an important moment for AI safety." It added that it was reviewing the incident with outside advisers and would eventually publish a technical report. "Does that mean that they left it unattended and didn't realize what it was doing? Or maybe they did and didn't know how to contain it? Both are equally dangerous and alarming," asked Marley Smith, the principal intelligence specialist at the nonprofit World Ethical Data Foundation. "The models lie, they cheat, they hack," said Jeffrey Ladish, whose organization, Palisade Research, studies the capabilities and motivations of AI agents. Ladish said the hack should spark broader questions over how much all the leading AI companies are willing to invest in onerous security measures while locked in a race with one another to deploy the best and fastest models. "There has to be government oversight," Ladish said, "because it won't happen otherwise."

Instagram Is Now Banning Pickup Artists, Pranksters Who Use Meta Glasses

Instagram is banning videos filmed with Meta smart glasses that harass strangers in public, including prank videos targeting service workers and pickup-artist clips of women who may not realize they are being recorded. "If you're posting content that is taking advantage of people and harassing them, like a lot of these pickup line kind of videos that we've heard of and seen, then we're going to take the content down," said Instagram head Adam Mosseri in response to a question on his Instagram stories last week. "We don't want people to be surreptitiously taking videos of other people and harassing them and then posting them on our platform. So we're trying to fight that every way we can." Business Insider reports: It's unclear how many videos have been removed under this new policy. Business Insider found that two large accounts of pickup artists who filmed themselves approaching women in public while wearing the glasses had been deactivated. (Both previously had more than a million followers.) A Meta spokesperson confirmed to Business Insider that these accounts were booted for violating the policy about posting harassing content that had been filmed with the glasses. Meta did not directly respond to questions about how this new policy is being enforced or what exactly constitutes a violation.

24 Jul 2026

Slashdot

Paramount Agrees to Postpone Warner Bros. Merger Until June 2027

Paramount Skydance has agreed to postpone its $111 billion Warner Bros. Discovery merger until five days after an antitrust trial or June 1, 2027, whichever comes first. The agreement with a 12-state coalition led by California effectively shelves the deal for months while states argue it would reduce competition in cable and theatrical markets. Variety reports: Paramount had been keen to close the deal before Sept. 30, when it will begin to incur a $7-million-a-day "ticking fee" to be paid to Warner Bros. investors. The agreement is a tacit acknowledgement that that will not happen, barring a settlement with the states. Paramount previously sought a three-day hearing on the injunction motion in late August, hoping to win the judge's blessing to close the deal sometime in early September. But the states resisted that idea, saying they would need more time to take discovery and prepare for a full trial on the merits. The states were due to file their injunction motion on Thursday night, but held off as the two sides held discussions on a path forward. In a statement, the company said the agreement is a "significant win." "Today's agreement is a significant win because the result is exactly what we have sought from the outset: a direct path to a trial based on the evidence," a Paramount spokesperson said. "This is the fastest and clearest way to prove that this transaction is good for competition, good for consumers, and good for creators, a conclusion dozens of competition authorities around the world have already reached. Plaintiffs' market definitions bear no relationship to the realities of today's marketplace and cannot withstand scrutiny. We look forward to proving our case at trial." A hearing was scheduled for Aug. 3 in federal court in Oakland, at which point the two sides were expected to argue over the injunction motion. The two sides agreed to cancel that hearing. U.S. District Judge Araceli Martinez-Olguin approved the joint stipulation on Friday afternoon, about an hour after it was entered. The Writers Guild of America filed its own motion for an injunction earlier this week, which was also set to be heard on Aug. 3. That motion has been withdrawn, as Paramount has effectively conceded that it will not close the deal until a determination of the merits of the antitrust claims. The parties also agreed to submit a joint stipulation by July 31 on their respective positions on trial scheduling. The states previously proposed to hold the trial in April 2027.

OSnews

The Hurd gets 9pfs, OpenNTPD, dynamic /dev/ entries, and more

The hottest and most promising operating system kernel in development, the GNU Hurd, has published another summary of its most recent quarter of development. Hurd has experimental support for 9pfs now, a work-in-progress port of OpenNTPD, the NTP daemon from OpenBSD, a port of Neovim, and a few more ports here and there. Diving deeper into the actual kernel itself, there's a major improvement to how the Hurd handles entries in /dev/: Mikhail Karpov added some checks for mmap in several places. He also worked on adding storeio to the bootstrap chain. This is actually quite interesting. Currently the Hurd sets device entries in /dev/ statically. For example, I am writing this qoth on a Hurd machine that is using two /dev/ entries for my filesystem: /dev/wd0s1 for swap and /dev/wd0s5 for my root filesystem. However, /dev/wd0s1 through /dev/wd0s16 exist on my computer! Once Mikhail's project is done, then the Hurd will dynamically populate SATA devices at boot time! No more need for static translators! ↫ The Hurd's quartely report The dhcpcd port we talked about earlier this year keeps improving too, which is quite important for future IPv6 support. Of course, there's way more to dive into, and reading about a bunch of people developing their own thing without any regard for or interest in the mainstream always feels a little bit like a cold glass of tonic - the best soft drink - in the depths of hell. Keep at it.

24 Jul 2026 10:44pm GMT

Ars Technica

Wildfire forces evacuation of NASA's Deep Space Network complex in Spain

"Any potential damage will be assessed when it is safe to do so."

24 Jul 2026 10:28pm GMT

OSnews

Google Play Services drops support for Android 6.0

Given that Android phones have been around for nearly two decades now, there comes a time when Google has to end support for one of its older software versions. For a couple of years now, Google Play services has been supported on devices running Android 6.0 Marshmallow or newer. That has changed over the past few weeks, with Google deciding to retire this software version after a nearly 11-year run. ↫ Chethan Rao at Android Authority At some point, an operating system version needs to be left behind - and I don't think it's entirely unreasonable to no longer support Google Play Services on an operating system version that's 11 years old. However, this is Android we're talking about, and devices running Android 6.0 were probably sold much more recently than 11 years ago, when the operating system version was new. Hell, I wouldn't be surprised if devices running Android 6.0 are still being sold today. I doubt this is something that will affect many people who read OSNews, but there's bound to be edge cases - Android 6.0 devices silently doing their job that are now just a little less useful. I'm thinking of really cheap tablets that can still play video just fine, retro gaming handhelds that don't magically lose the ability to emulate SNES games, that sort of stuff. The numbers will be small, but if you happen to be among them, this can be a really annoying deprecation.

24 Jul 2026 10:22pm GMT

Ars Technica

Paramount/WBD merger delayed for months as states' lawsuit moves toward trial

"Halting this merger while our case proceeds is a critical victory," NY AG said.

24 Jul 2026 9:56pm GMT

Canadian legislator reads out apparent LLM response in floor speech

"Here's a more natural, flowing version of that section..."

24 Jul 2026 9:25pm GMT

23 Jul 2026

OSnews

FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary

A rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here's why. A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. ↫ Kyle Evans in freebsd-announce While FreeBSD's ports tree is not hosted by GitHub - it's merely mirrored there - the FreeBSD team believes the community values the GitHub mirror too much, and as such, steps had to be taken to fix this. Ports has not been compromised and users' systems do not appear to be at risk in any way due to this occurrence, which is good news. Curiously, the official announcement makes no mention of which 150MB file, exactly, was committed to ports, but it didn't take for people long to pinpoint the offending commit (screenshot). It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. This FreeBSD port is effectively a way to easily install and run this tool on FreeBSD using Linuxulator, FreeBSD's Linux compatibility layer that allows you to run unmodified Linux binaries on FreeBSD. It's important to note this FreeBSD port is not actually a port of the Linux version of github-copilot-cli to FreeBSD; the FreeBSD "port" merely acts as a setup script to run the unmodified Linux binary using Linuxulator. It's not a "real" port because the tool isn't open source and its license doesn't allow for modifications. That's why the announcement specifically mentions "questionable licensing" - github-copilot-cli is licensed under some custom license specifically made for this tool, and is not open source. Anyway, for whatever reason, the maintainer of this FreeBSD port accidentally made a commit that added the actual, full 150MB Linux binary to FreeBSD ports. I'm assuming that under normal circumstances, building and installing the github-copilot-cli FreeBSD port would merely download the binary off GitHub and set Linuxulator up so that it could run it. Mistakes happen, and since there's clearly nothing malicious going on, there's not much to worry about. In fact, this may lead to new checks and balances to prevent this from happening in the future, which would be good news. The FreeBSD team is working on rolling back, fixing the issue, and investigating how this could have happened. Ports is still frozen at the time of writing, but I'm sure we'll have a more detailed account soon.

23 Jul 2026 8:33pm GMT