A New Mexico judge has ordered Meta to pay $25 billion after a jury found Facebook liable for deceiving users about privacy during the Cambridge Analytica scandal. State Attorney General Raul Torrez called it "one of the largest, if not the single largest state verdict against a company in American history." While Meta plans to appeal the ruling, the funds that are to be collected will go toward state education spending. The Associated Press reports: Jurors in September found Meta liable for over 43 million violations of New Mexico consumer protection laws when a political consulting firm, Cambridge Analytica, harvested Facebook user data to generate targeted political ads for the 2016 election. Forty-eight other states settled with Facebook in a nationwide case, but New Mexico chose to take the social media company to court on its own. [...] During the trial, jurors assessed whether Facebook misled users about privacy and content moderation 34 separate times. State prosecutors, though, argued Facebook's statements deceived the entire population of New Mexico and extended beyond social media users.

In the end, jurors agreed with this premise and found Facebook liable for 2.1 million violations on certain counts, bringing the total number of violations to over 43 million. Facebook's attorneys have argued in subsequent court filings that the state's consumer protection laws don't apply to people in New Mexico who weren't using the platform at the time. [...] In one of the few wins for the defense, jurors found the state didn't prove that Facebook made false claims about removing harmful content, including misinformation about the COVID-19 pandemic.

The state said the company favored certain accounts and allowed for violent or inaccurate content to proliferate. Attorney Randi McGinn said in her closing argument for the state that Facebook profited off harmful content, which CEO Mark Zuckerberg denied during his video deposition. Zuckerberg said the company has to carefully balance freedom of speech with content moderation. Attorneys for Facebook said the company has adapted its policies since the state's lawsuit was filed in 2021 and that it removes 99% of content that violates standards.

OpenAI is bringing its models to Google Cloud's model garden and Antigravity coding tool, putting its technology on all three major U.S. cloud platforms after Microsoft's exclusive license ended earlier this year. "Google Cloud's longstanding investment in machine learning and AI has made it a destination for AI workloads and the developers and data scientists building them," OpenAI said in a blog post. It continues: [...] The integration will pair OpenAI's frontier models with Google Cloud's built-in access controls, centralized data governance, and high-performance infrastructure to support demanding enterprise workloads.

Google Cloud customers will be able to purchase OpenAI frontier models via model garden, transacted through the Google Cloud Marketplace. Enterprises with Google Cloud spend commitments will be able to draw down their GCP commitments for these purchases.

Additionally, OpenAI models will soon be available in Google Antigravity and the Gemini Agent, providing enterprise customers with model choice flexibility and the best model for each task. [...] For context, Microsoft previously held exclusive licensing rights to OpenAI's intellectual property, but that arrangement ended less than six months ago as OpenAI began expanding its partnerships with other cloud providers.

Just one day after Microsoft's exclusivity ended, Amazon announced plans to host OpenAI's models on its cloud platform in April.

"PHP disclosed two critical vulnerabilities in their programming language and urged web site operators to immediately apply the fix," writes longtime Slashdot reader smooth wombat. "As a result, government web sites in Europe and elsewhere temporarily went dark on Wednesday as operators worked to protect their systems." The Independent reports: Dane Knecht, the chief technology officer of Web and cloud security firm Cloudflare, said that attacks were emerging and Cloudflare was updating its firewall rules as a stopgap measure. "We are seeing early attacks emerging and are updating mitigations as new vectors show up. This is a STOPGAP only. Patch as soon as PHP releases the update," he said on X.

Officials have said that all PHP versions from PHP 5 onward could be affected, although PHP has not yet disclosed which versions are vulnerable. Special thanks to Slashdot readers Alain Williams and mrspoonsi for sharing this critical PHP security release.

For more details, read the official PHP announcement and guidance on what to do next.

An anonymous reader quotes a report from Ars Technica: Website admins, brace yourselves. Fixes for what are believed to be uncommonly severe vulnerabilities are scheduled to drop in a little more than 12 hours for PHP, a programming language that powers websites and Web applications everywhere. PHP maintainers said Monday that they planned to release patches for two vulnerabilities, both with severity ratings of 9.2 out of a possible 10.

"All PHP users are encouraged to prepare now so they can upgrade as soon as the release is available," the advisory stated. "We reserve the right to release earlier should details of either vulnerability become public, or should evidence of active exploitation appear in the wild." The maintainers published the advisory following the leaking of purported details, which have yet to be confirmed. The report showed a video of an exploit tool dubbed PHP2Shell executing code on webservers running WordPress 7.1.3, MediaWiki 1.46.2, phpBB 3.3.17, Magento 2.4.9, Joomla 6.2.0, Laravel 13.36.0, Laravel 8.83.29, Symphony 8.1.9, Drupal 11.4.10, and WHMCS 9.0.9, all of which use PHP. A video depicting the tool has been reposted here.

Attempts to locate the unconfirmed report were unsuccessful, but security firm watchTowr said it claimed to affect every PHP version from PHP 5, released in 2004, onward. The security firm went on to say it has confirmed that the vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, are real. Researchers from separate security firm Sansec said they "expect mass attacks to start within 15 minutes of the release." A third security firm, Webfence, also urged admins to prepare now. Huntress has also issued an advisory.

Elon Musk says a merger between Tesla and SpaceX is under active consideration, with special committees at both companies evaluating a deal that could combine businesses valued at roughly $3.5 trillion. "Do I think it would be a good idea? Yes," Musk said during a call with financial analysts over the quarterly business results of SpaceX on Tuesday. The BBC reports: While Musk noted the certainty of such a merger should not be assumed, and it would need shareholders' support, he said special committees within both companies have been formed to examine the move. "The special committees have not reached agreement on terms of any transaction and there's no guarantee that they will," Musk added. "But I do think there is a lot of merit to merging and a lot to be gained."

[...] The company, which builds space rockets and Starlink internet satellites, is now expanding into offering cloud compute capacity for other tech companies, like Anthropic and Google. That line of business has become the most profitable part of SpaceX, bringing in $7.5bn according to the latest quarterly results (PDF). Starlink also tallied revenue of $5.2bn. SpaceX as a whole, however, is not profitable and has lost $1.1bn so far this year.

[...] Musk said on Tuesday a full merger between the two companies would make sense for the work each is doing around chips, artificial intelligence, software and more. He described himself as a "conflicted party" as the chief executive of Tesla and of SpaceX. Even commenting on the possibility of a merger between the two companies, Musk compared to "tap dancing through a minefield." He added a merger would ultimately be decided by shareholders. At least 50% of Tesla's shareholders would need to approve the merger, which Musk described as "quite a high hurdle to achieve."

Longtime Slashdot reader schwit1 shares a report from TWZ: A Russian satellite, Kosmos 2612, may have passed within approximately 85 feet (26 meters) of a U.S.-registered satellite belonging to commercial imagery provider ICEYE. This would be an extraordinarily close and potentially dangerous pass-by for two objects in space traveling at thousands of miles per hour. For weeks beforehand, ICEYE-X36, which would be of special interest to Russia, had already found itself in increasingly close orbital alignment with its pursuer. The two satellites now look to be drifting further and further apart, but the episode has been a clear sign of what is to come as the potential for conflict in space only continues to grow.

Publicly available space tracking data from the satellitemap.space and orbitalradar.com websites show that Kosmos 2612 (also written sometimes Cosmos 2612 and abbreviated K2612) and ICEYE X36 had their especially close encounter at approximately 16:07 UTC today. Private space services company LeoLabs also told TWZ today that it could not "confirm or contradict what other data sources have stated publicly," but that it has "high-confidence that the objects came within approximately [emphasis in the original] 500 meters [1,640 feet] of each other." Kosmos 2612 had been making progressively closer passes by ICEYE X36 in recent days. "This is the most advanced and potentially dangerous uncooperative RPO we've observed," Adam Marsh, LeoLabs vice president for technical solutions, separately told Breaking Defense.

"It's important to note that 'red' on 'blue' engagements, such as this, are relatively uncommon in Low Earth Orbit (LEO)," LeoLabs' report points out. At the same time, "this was not a routine conjunction or 'fly by.' The sequence included a controlled approach, changes in relative position, close-proximity loitering, additional small maneuvers, and a controlled departure. The behavior is consistent with sophisticated rendezvous and proximity operations (RPO)."

"We can only speculate about the operation's goal, but it could have been anything from simply intimidation to outright destruction or sabotage of a U.S.-registered satellite," CSIS' Clayton Swope told TWZ. "Perhaps the operation is on hold. There are, however, several other satellites that shadowed ICEYE X36 back in May that could be brought in[to] action too."

An anonymous reader quotes a report from TorrentFreak: Last month, Magistrate Judge Thomas Hixson ordered Meta to hand over the command histories of the servers it used to torrent pirated books. These logs would presumably reveal how Meta's torrent clients were set up, including any changes to their upload settings. [...] The server logs could reveal what happened on Meta's machines. However, publisher Entrepreneur Media also wants to know who approved the torrenting activity.

Entrepreneur Media, which publishes Entrepreneur magazine, filed one of the related lawsuits where it accuses Meta of contributing to piracy by uploading (seeding) works to third parties, similar to the authors' contributory infringement claim. To find out more, the publisher asked Meta to identify everyone who "made, authorized, or approved" the decisions to obtain the shadow library datasets, and to do so via BitTorrent.

Meta's answers named several people who are believed to have been involved in data-related decisions. However, Meta said it couldn't identify anyone who "formally" made or approved decisions to acquire or use books for its first two Llama models. Those decisions were often the result of team consensus, Meta argued. When it came to the torrenting itself, Meta pointed to the employees who ran the downloads, describing their choices as technical decisions.

Meta added that the acquisition of data from Anna's Archive went through an internal legal review in early 2024, which involved its in-house lawyers. In other words, the company didn't name anyone higher up who approved the use of BitTorrent. "On that construction no one at Meta decided to torrent anything, yet Meta torrented shadow libraries repeatedly from 2022-2024," Entrepreneur Media countered. An internal Meta logbook warned that using torrents would involve sharing copyrighted material with others. "Using torrents would entail seeding the file such as sharing content outside. This would be legally not okay," the logbook stated.

Although Meta admits downloading data from LibGen and Anna's Archive via BitTorrent, it claims no one "made, authorized, or approved" a decision to distribute the material and that measures were taken to limit seeding. Meta's own expert previously estimated that uploads from its AWS servers amounted to no more than roughly 30% of the data downloaded during a period in 2024.

Judge Thomas Hixson is not convinced and ordered (PDF) the company to identify everyone involved in approving the downloads, including those who decided "whether or how to seed, or to mitigate seeding."

Ukraine says it carried out the world's first evacuation of a wounded soldier by aerial drone, using a heavy-lift hexacopter after enemy drones and landmines made conventional ground evacuation too dangerous. NBC News reports: Shared by the 92nd Separate Assault Brigade on Monday, the video shows the soldier strapping himself into a large drone and being flown at what appears to be relatively low altitude over blurred-out territory. The drone carefully lowers him, and the drone operator greets him with "Welcome back to the ground!" The video also shows blurred faces of drone operators who carried out the mission.

The post said the unidentified infantryman was wounded at his position. "Due to intense enemy drone activity and the presence of landmines, evacuation using conventional unmanned ground vehicles was impossible," the brigade said. "At that point, the specialists in our unit took it upon themselves to attempt something that had never been done before: evacuating a serviceman using an aerial drone," it added.

The craft was a heavy-lift hexacopter, it said, originally designed as a bomber by a Ukrainian manufacturer. It looks about twice the size of the soldier in the video. The specialists working on the mission had to ensure the drone could carry a human being without flipping over or swaying excessively, according to the unit.

Sony has revived its Walkman lineup with three Android 16-powered high-end music players ranging from $1,900 to $5,900, topped by the gold-plated NW-WM1ZM3 with 256GB of storage. The Register reports: The Japanese giant named the new models the NW-WM1ZM3, NW-WM1AM3 and NW-ZX900. All can store and play many codecs, including MP3s, WMA, and FLAC files, plus others like Direct Stream Digital (DSD) and Apple Lossless, which use various tricks to avoid nasty artefacts accruing during the digitization process. Sony also says it has used "key components made from oxygen-free copper" because that apparently delivers "uncompromising sound quality."

The machines also include "screws featuring a low-resistance gold-plated treatment ... providing a stable ground connection that delivers powerful bass, an expansive soundstage and smooth, extended high frequencies." Sony claims even the cabling it's used in the devices "further reduces noise and preserves signal integrity for rich, detailed sound." They're also housed in carefully-milled slabs of copper -- gold-plated in the case of the NW-WM1ZM3 -- because that apparently improves sound, too.

And then Sony's gone and spoiled it all by offering Bluetooth connectivity, a notorious music-mangler, in addition to wired headphone ports. Sony's US site lists all three devices, which run Android 16 and include Wi-Fi so they can access streaming music services. All are USB-chargeable and Sony claims their batteries allow 30-odd hours of music playback.

AMD is expanding its FSR 4.1 upscaling technology beyond Radeon RX 9000-series GPUs to Xbox Series X/S consoles, Xbox Ally handhelds, laptops, and Radeon RX 6000-series graphics cards. The Verge reports: AMD launched its FSR 4.1 update for Radeon RX 9000-series graphics cards in March, and promised to bring the technology to older GPUs and handhelds this year. FSR 4.1 can improve performance in more than 300 supported games, including Cyberpunk 2077, Battlefield 6, and Assassin's Creed Shadows.

[...] While owners of Radeon RX 6000-series GPUs and Gorgon Halo- or Strix Halo-powered devices will get FSR 4.1 today with the latest Adrenalin Edition 26.10.1 drivers, Xbox console owners will have to wait a little longer. "We've worked very closely with AMD to optimize this technology, giving developers another powerful tool for great performance and visual quality for players," says Xbox CTO Scott Van Vilet.

Google is beginning to replace traditional support articles with "Ask Google Help," a Gemini-powered interface that summarizes documentation and lets users troubleshoot through a chatbot. 9to5Google reports: "Ask Google Help" will display a condensed version of the support article with direct troubleshooting steps, with the user then able to type in queries to have Gemini help figure out the next step forward. A "View Sources" button at the bottom of the AI response allows users to still access the original article, but direct links to any of these articles now defaults to the AI experience.

An example can be seen below on the "Secure a hacked or compromised Google account" page that Google's own support account directed users to within the past few days. It can also be seen on the "Fix common issues with 2-Step Verification" page and, as far as we can tell, any support pages on the Google Account Help forum.

Google, as of right now, appears to only be testing this on select support topics. The Google Pixel Help section, for instance, still defaults to articles, whereas the Google Chrome topic has also moved to the new experience. Beyond support pages alone, this new design also impacts the central hub, with links to topics no longer showing by default in exchange for an AI chatbot that helps you find the relevant page.

New court records reportedly show that DHS targeted Stop Cop City activist Samuel Tunick at an Atlanta airport because he was under investigation for suspected "terrorist activities." However, the CBP officers told him instead that they wanted to search his phone for child sexual abuse material (CSAM). Tunick, who is not accused of terrorism or any other crime beyond allegedly wiping his GrapheneOS phone during the encounter, faces up to five years in prison. 404 Media reports: Instead of saying he was being targeted for suspected terrorism -- although this search happened just at the start of the second Trump administration, it has dramatically broadened what organizations or people may be considered such -- they said they needed his phone to look for "kiddie p*rn." "Good afternoon," an email sent from a Homeland Security Investigations (HSI) official, part of Immigration and Customs Enforcement (ICE), to CBP and other officials reads. "The following subject is scheduled to arrive in ATL [Hartsfield-Jackson Atlanta International Airport] today via DL 1778 @ 1930 Hours. TUNICK is under investigation by HSI/JTTF for suspected terrorist activities." The email includes a photo of Tunick, and asks the officials to direct him to secondary inspection, retain all of his electronics, and collect their passcodes.

As 404 Media first revealed in December, Tunick was charged because he allegedly "did knowingly destroy, damage, waste, dispose of, and otherwise take any action to delete the digital contents of a Google Pixel cellular phone, for the purpose of preventing and impairing the Government's lawful authority to take said property into its custody and control." Matthew Dodge, one of Tunick's lawyers, previously told 404 Media he only found one other case using the same obscure law, a drug trafficking case. "This is extraordinarily rare," Dodge said.

Tunick was part of the Stop Cop City movement in Atlanta, which broadly protested the building of a large police training center, and which authorities investigated for arson, vandalism, and doxing. Tunick is not suspected of any crime beyond the alleged wiping of the phone, and has previously put his current prosecution in the context of the wide spanning cases against other Stop Cop City protesters. The newly filed court record, in which Tunick's lawyers argue that evidence should be thrown out, include new photos and descriptions of the airport encounter. The CBP officials asked Tunick if they were going to find "kiddie p*rn" on his phone, which Tunick immediately denied. "As the evidentiary hearing made clear, these unfounded accusations were nothing more than pretext for a fishing expedition into the depths of Mr. Tunick's devices," the lawyers wrote. They added, "Officer Findley acknowledged that officers had no reason whatsoever to believe Mr. Tunick possessed child p*rnography," referring to one of the officials.

OpenBSD 8.0 has been released with major virtualization and hardware upgrades, including support for up to 64 vCPUs per VM, Intel Arc graphics, ARM64 hibernation, and expanded RISC-V support. Linuxiac points out that it marks the "61st release of the security-focused Unix-like operating system." From the report: Several fixes improve compatibility with 32-bit Linux guests, while changes to virtual machine ownership management and interrupt emulation make the virtualization infrastructure more capable. Graphics support has also been upgraded, with DRM drivers updated to those from Linux kernel 6.18.53. Notably, OpenBSD 8.0 adds support for Intel Arc A-Series (Alchemist) graphics cards through the inteldrm driver.

Another important change increases the amd64 kernel's virtual address space from 4 GB to 512 GB, allowing the system to map over 4 GB of video memory. The release also addresses GPU timeout issues affecting some Intel Alder Lake systems. [...] For security, OpenBSD 8.0 adds checks and fixes across the kernel and system utilities, including improvements to pledge and unveil, tighter validation of executable files, and protections against memory corruption and information disclosure. A full list of changes can be found here.

Further reading: Wine Ported to OpenBSD

Security researchers say Meta's Muse AI assistant exposed thousands of users' shared conversations because conversation titles were placed in subdomains that could be discovered through public DNS records. Meta has since suspended the sharing feature while it considers making changes. Ars Technica reports: Like many online services, Muse has allowed users to share searches, conversations, images, and similar content with other people. Such share features usually involve clicking an option to create a unique URL that anyone can use to load a page hosting the content. To keep potentially sensitive information from being accessible to unintended people, the URLs typically contain a long sequence of text that can't be easily guessed.

Muse, which Meta CEO Mark Zuckerberg said last month was "built from the ground up for privacy and security," seems to take the same precautions. But a central design decision for constructing URLs has made the links easy to discover. As a result, researchers from security firm Claroc said they were able to enumerate 6,800 links Muse users created for sharing conversations with others. After opening a few hundred of them, the researchers found information that was clearly not intended to be publicly available... [...]. "If you had asked us beforehand, we would have guessed that gathering these would take real effort," the researchers wrote. "It took one query."

[...] The easiest way to discover the URLs is to perform a passive DNS search through one of many available commercial services. Passive DNS records store the historical resolution of domain names to IP addresses, as well as nameserver, and mail-server records over time. Passive DNS systems typically collect DNS responses from sensors positioned at recursive DNS resolvers or other infrastructure. A passive DNS record is generally created when a monitoring system observes a DNS response. In the case here, once the intended party clicks on the share link, the DNS information is recorded in a searchable database.

Claroc researchers were able to discover the Muse share links because all of them use the domain name cf.metaaiusercontent.com. Discovery is further made easy by the decision to add the conversation name to the URL, along with a long string of text. Simplified examples of such links are home-sale-budget-9f21c8a3.cf.metaaiusercontent.com, q3-revenue-review-7b1e42f0.cf.metaaiusercontent.com, and loan-application-draft-a4c9e2.cf.metaaiusercontent.com. It's this last design decision, putting the conversation title in the subdomain rather than in the URL path, that makes public discovery possible.