US Bank says that it's investigating ransomware crew LockBit’s claims that it breached the financial institution and stole data, which the crims threaten to leak on September 3 unless the bank pays an extortion demand. "We have investigated this matter and the available evidence indicates that the claim regarding a potential cyber incident is related to a fourth party event that occurred outside of our environment. At this time, there is no evidence that our systems, networks or data repositories were compromised," Lee Henderson, US Bank VP of public affairs, said in an emailed statement to The Register. If the extortionists’ claims are true, and even if the bank pays the ransom demand, there’s still no guarantee that the digital thieves will delete the stolen files. When cops took down an earlier iteration of LockBit in 2024, they found evidence that the crooks retained victim data - even after the victims paid the extortion demands. “We have provided relevant information to law enforcement and continue to support their investigation," Henderson continued. "The security and privacy of our customers’ information is our highest priority. We will continue to provide updates as warranted.” LockBit added the bank to its leak site late Wednesday night, and gave the bank 14 days to pay a ransom demand or else see its data dumped online. The post doesn’t say how many files the crew allegedly stole, or what they contained. In February 2024, international cops seized servers, domain infrastructure, and decryption keys in an effort to dismantle the notorious ransomware group, and in May 2024, they outed LockBitSupp's true identity - although Dmitry Yuryevich Khoroshev, a Russian national, remains at large. In September 2025, however, LockBit reemerged with its new LockBit 5.0 ransomware variant. LockBit’s latest claims follow previous third-party breaches affecting US Bank customers’ data, and at least one law firm says that it’s considering a class-action lawsuit against US Bank National Association, the primary banking subsidiary of US Bancorp, on behalf of a small group of customers whose credit card information may have been exposed in a third-party security snafu that reached the bank through its vendor, Fidelity National Information Services. US Bank reportedly found out about the third-party incident on May 7, and in June, began notifying 537 customers, all Massachusetts residents, that their names, mailing addresses, and credit card numbers may have been stolen by the digital crooks. Customers’ Social Security numbers, online banking credentials, and account balances reportedly weren’t accessed. A much larger incident affecting around 11,000 customers occurred in 2022, after a different vendor “accidentally shared” a file containing personal information associated with closed US Bank credit card accounts, including names, addresses, Social Security numbers, dates of birth, closed account numbers, and outstanding balances.® Updated on Aug 21 with a new statement from US Bank.

A young security researcher figured out a way to enroll a Linux device into Apple’s Find My network and read live location data from it. Find My is Apple’s app for, you guessed it, finding things – whether AirTags, iPads, or other supported devices and items. It also works for people. Families can track each other's whereabouts for safety reasons, and friends can tell when others are hanging out without them. In typical Apple fashion, though, the full Find My experience is limited to Apple hardware, like an iPhone or Mac. iBiz also offers Find Devices via the iCloud website, although it lacks Find My’s people-tracking feature for viewing locations others have shared with you. However, the 22-year-old researcher, who goes by “Zerotistic,” devised a way to enroll a Linux-based machine into the iNetwork, tricking Apple into sending the people-location data it exclusively reserves for Apple devices. It’s important to note, at this point, that this is not an exploit that allows anyone to arbitrarily retrieve any Apple user's location. It refers to registering a non-Apple device to the Find My network and retrieving the location data of people who had already chosen to share their locations with the Apple account owner. Retrieving people-location data requires Apple to trust that the machine you’re using belongs to its network and is capable of receiving the data, which is sent over Apple’s Push Notification service (APNs). The first step was tying the Linux machine to the researcher’s Apple account. Zerotistic obtained an identity delegate by going through Apple’s standard GrandSlam authentication protocol. In pursuit of an Apple Identity Services (IDS) device certificate, which links the intended device to an Apple Account, they then used that delegate to build a custom certificate signing request (CSR). Lots of trial and error later, Zerotistic discovered that the CSR had to use the PKCS#10 format and a 2048-bit RSA key signed using SHA-1, linking the Linux machine to their Apple account. They bundled this up into a compressed XML file and sent it to Apple’s authenticateDS profile-enrollment endpoint. The SHA-1 signature requirement and XML encoding were surprises. The researcher’s “best guess” is that the CSR had to conform to older standards because authenticateDS is a legacy endpoint. Apple signed the CSR, handing the Linux device the IDS certificate needed to register its public key to the researcher’s Apple account. The Linux device was registered at this point, but further work was needed to convince Apple that it was capable of running Find My. Zerotistic found that a Find My registration request required the device to subscribe to six different subservices, define the types of encryption it supported, and provide the public keys to support Apple’s device-to-device messaging format. It also had to be signed using an IDS certificate and an APNs certificate obtained during initial network setup. At this point, the researcher had enrolled the Linux machine in an Apple account and convinced Find My that it was capable of receiving location data via a persistent binary TLS connection to Apple’s private APNs servers. However, this registration did not automatically retrieve the location data of people who had previously shared their locations with Zerotistic, as a box-fresh Apple device would after setup. Issuing a SubscribeAndFetch request fixed this, prompting the device of the researcher’s friend to push an encrypted location key to the newly registered Linux device. The final challenge was reading the location data the Linux device fetched from Apple’s SearchParty service. Zerotistic was not simply using the GUI Find My app on Linux; they were receiving the encrypted data and had to figure out how to unpack the location message. This required a Linux script to unwrap Apple’s messaging envelope, extract the shared location key, and decrypt the Find My location data, which is comprised of coordinates, timestamps, and accuracy information. Once developed, the script could fetch and decode subsequent location reports for the existing location share. It took the researcher less than a week of tinkering to develop the Find My-busting technique, they said. The Register asked Apple if it was aware of the researcher’s work and if it had any plans to address the issue, but it did not immediately respond. ®

France's tax authority says attackers may have stolen the contents of messages exchanged with hundreds of taxpayers during the data raid it confirmed last week. In an update published this week, the General Directorate of Public Finances (DGFiP) said lists of messages exchanged with the authority were exposed. For around 250 people, the compromised information also included the messages themselves. Slightly more than 350,000 individuals were affected. The other exposed data included tax identification numbers, marital status, email and postal addresses, and phone numbers. Tax records also exposed details such as household composition, number of dependents, family quotient, reference tax income, and withholding rates. Beyond the personal and tax information, DGFiP said the other affected datasets contained information that was already publicly available. For approximately 250,000 businesses and professionals, the affected data was limited to company names and SIREN numbers, the unique nine-digit identifiers assigned to French businesses. The compromised cadastral data was limited to property addresses and dimensions, which DGFiP said were already publicly available. DGFiP said it was notifying affected taxpayers by email or post this week. DGFiP's latest FAQ pegs the total number of affected parties at roughly 600,000. That appears lower than the 678,000 "individuals and professionals" DGFiP said were affected last week, shortly after the alleged cybercriminal behind the attack, "ZeroBytes," claimed to have stolen data belonging to more than 2 million. The authority did not explain the discrepancy. The notifications warn that criminals could use the stolen details to make phishing attempts appear more convincing. DGFiP highlighted impersonation attempts, CEO fraud, and scams involving bogus bank advisers as possible follow-on attacks. The authority said it would never ask taxpayers to provide sensitive information such as PINs or identity documents by phone, text message, or email, and would request such material only through its secure portal. Separately, the tax authority disclosed a "technical vulnerability" in the government's Vacant Successions Portal (PSV), which is used to search for estates without known heirs. DGFiP suspended the service after discovering the flaw. It said there was no evidence so far that personal data had leaked, although its investigation into possible exposure of applicants' details continues. The incident adds to a torrid year for cybersecurity across France's public sector. In February, the finance ministry, which oversees DGFiP, 'fessed up to an intrusion into a database containing citizens' bank details that affected 1.2 million people. The Health Ministry confirmed in March that 15.8 million administrative files, 165,000 of which contained doctors' notes, were stolen during an attack on healthtech company Cegedim Santé. A month later, a 15-year-old allegedly carried out an attack on France Titres, which handles the country's identity documents. The attacker claimed the breach affected between 18 million and 19 million people. In June, France also began probing an alleged breach of Tchap, the government's encrypted messaging platform, after attackers claimed to have accessed 73,000 user accounts, 643,000 messages, and nearly 60,000 media files. ®

PWNED Welcome back to PWNED, the column where we make fun of those who are security self-owned, so hopefully you don’t do the same. This week, we have a story that’s hot off the presses about a company almost sabotaging its security by using AI for programming. Have a story about someone leaving a gaping hole in their network? Share it with us at pwned@sitpub.com. Anonymity is available upon request. Our tale of machine learning malfeasance comes courtesy of Sergiy Fitsak, managing director of Softjourn, a consulting and software development company. He reminds us that, when it comes to AI, don’t trust: verify. During the course of business, one engineer asked an AI agent to recommend a package that they needed for a common task. The agent came back with the name of a legitimate-sounding package, which was formatted like a familiar library. At many organizations, this would have been the end of the story. The developer would have taken the AI agent’s advice and downloaded and installed the recommended package. However, at Softjourn, the company has a policy which they actually followed: double-check any software recommendations made by AI to make sure they are legit. The developer skimmed the recommended package’s source code on GitHub and noticed that it had few downloads and had just been created a few days earlier. In other words, it was suspicious. According to Fitsak, attackers have found a way to exploit package names hallucinated by AI models. “The problem is that AI models sometimes invent package names that sound plausible but don't exist, a pattern security researchers have started calling 'slopsquatting,'” he told us. “Attackers have caught on and now register real packages under those exact invented names, betting that a developer under deadline pressure will install first and check later.” If Softjourn hadn’t been so careful, they could have installed a malware package. We don’t know the exact payload, but this malware package could have given crims a backdoor into their systems and the ability to steal data or wreak other havoc. “We caught it because we'd already built a habit of verifying download counts and reviewing source code on GitHub before installing anything an AI recommends, even when it looks routine,” Fitsak said. “It takes a few extra minutes. Skipping that step once is how a team ends up explaining a supply chain compromise instead of shipping a feature on time.” The lesson here is a very simple one: Don’t trust the package names that AI agents recommend. Have a human check the supply chain. And always have a human in the loop so they can take the time to stop and approve any outside code that comes into a project. ®

Attackers are using AI-generated exploitation scripts to break into internet-exposed Siemens S7 Series programmable logic controllers (PLCs) at water, manufacturing, energy, and other critical facilities, in what five US federal agencies on Wednesday called an “active threat.” In this latest round of intrusions against American critical infrastructure, the attackers use open source industrial automation libraries – specifically snap7.dll/python-snap7 – combined with AI coding assistants. Armed with the open source libraries and AI, the miscreants create custom tools that mimic operational technology (OT) monitoring software and provide read/write access to the PLC devices’ memory, configuration data, and ladder logic programs via the S7comm protocol. “This is not a theoretical risk – it is an active threat,” the feds warned. While the joint alert from the National Security Agency (NSA), Cybersecurity and Infrastructure Security Agency (CISA), Federal Bureau of Investigation (FBI), Department of Energy (DOE), and Environmental Protection Agency (EPA) doesn’t attribute the threats to a particular government or criminal group, Iranian cyber operatives are suspected of being behind recent attacks targeting PLCs at water and wastewater facilities across at least 12 states, including a cyberattack that disrupted more than 30 community water systems in Minnesota in late July. “This appears to be a continuation of the same suite of activity we suspect is affiliated with Iran targeting PLCs,” Cynthia Kaiser, Halcyon Ransomware Research Center SVP, told The Register. “Iran-affiliated actors and adversaries are actively targeting a wide swath of operational technology because these PLCs underpin essential health, safety, and critical infrastructure across society.” National security and infosec experts last week told The Register that while there is no indication that the water-system hackers used AI in their intrusions, they worried that attackers would soon add AI to their arsenals for attacks against critical infrastructure. Now, that threat appears to be here. “What the advisory highlights with regard to AI usage aligns with what we’ve expected: state-sponsored adversaries are leveraging AI across the board for discrete tasks, like code checks and scripting, to scale their operations and move faster,” Kaiser, a former FBI cyber division deputy assistant director, told us on Wednesday. “The advisory reflects the broader reality that threat actors are using AI to increase their efficiency.” Siemens S7 Series PLCs under fire According to the Wednesday security alert, the latest attacks specifically target internet-exposed Siemens S7 Series PLCs across critical manufacturing, energy, water and wastewater, chemical, food and agriculture, and commercial facilities – in other words: most of the critical industries providing goods and services that Americans use in their daily lives. “Additionally, Siemens S7 Series PLCs are used in other sectors, including the Defense Industrial Base (DIB), and could be targeted there as well,” the feds warned. The Register reached out to the agencies for additional information about the attacks but did not receive any response to our questions. Attackers use internet-scanning services such as Censys and ZoomEye to find exposed, “poorly protected” PLCs running outdated software or using default passwords – and now they’ve got an AI boost. “Threat actors are using AI assistance to generate exploitation scripts using publicly available information on these Siemens S7 Series PLCs for initial access, credential access, denial of service, and other objectives,” the agencies said. “If these PLCs are exposed to the Internet or insufficiently segmented, then threat actors can exploit various critical and high severity known vulnerabilities in these PLCs.” The use of AI also indicates “an evolution in threat actor capabilities,” reducing the need for advanced technical knowledge about OT, and allowing the attacker to more rapidly develop working industrial control system malware and attack chains, the alert says. “I think that the bigger issue is still how exposed OT environments are,” Benny Czarny, CEO and founder of critical infrastructure security firm Opswat, told The Register in an email. “AI makes it much easier for an attacker to create and modify scripts targeting PLCs, so the barrier to attacking industrial systems continues to fall. But for me the answer is not simply better AI detection.” To mitigate this threat, the feds say critical infrastructure owners and operators should first – immediately – inventory all Siemens S7 Series PLCs in their environment, apply security patches as needed, and make sure no PLCs are accessible from the internet. It's also worth checking for anomalous S7comm behavior, including connections from non-engineering workstations, unusual data block access patterns, or write operations outside change windows, the feds suggest. Sequential IP scanning on port 102 and repeated connection attempts with varying parameters can indicate attackers conducting reconnaissance, and Snap7.dll library usage outside approved workstations may also indicate the presence of intruders on the network – so be sure to use these and the rest of the detection strategies detailed in the government security advisory to hunt for anomalies that may indicate a compromise. In addition to looking for indicators of compromise relevant to these intrusions, Czarny said it's critical to reduce the OT attack surface. “If data only needs to leave an OT network, use a data diode,” he said. “There should be no network path back to the PLC for an attacker to exploit. Yes, AI makes this more urgent. But the real lesson for me is still the same: stop giving attackers a path to the critical system in the first place. And do not rely on antivirus and sandboxes to protect your data flow.” ®

Some ICE employees seemingly needed a reminder not to wear their Meta pervert glasses to work. Because only ICE can spy on ICE. Meta smart glasses are essentially “body-worn cameras,” as they can covertly record video and audio, David Venturella, Immigration and Customs Enforcement acting director, reportedly reminded agency employees on Tuesday. “The use of Meta Glasses or similar devices could unintentionally capture, record or transmit sensitive information, potentially compromising privacy and legal protections,” Venturella said in a Tuesday memo, according to a New York Times report. ICE policy [PDF] prohibits employees from using personal body-worn cameras in the workplace. As such, ICE employees’ personal Meta glasses - along with similar wearable devices capable of recording audio or video - are banned from use on the job. An ICE spokesperson told us that ICE, on occasion, reminds its employees of existing policies like this one, and that the agency takes privacy and operational security seriously. “This isn’t news - nothing has changed,” an ICE spokesperson said. “Personally owned body-worn cameras and unauthorized recording are prohibited, as they always have been.” The spokesperson declined to answer The Register’s questions including what prompted the reminder and whether more ICE agents have been bringing their Meta glasses to work. Meta said it had no comment on the story. While the ICE policy isn’t new, the outright ban on Meta’s so-called pervert glasses has been trending upward since DEF CON told hackers to leave any glasses equipped with recording capabilities at home. “Be sure to pack non-violating eyewear if you need them,” DEF CON organizers told conference attendees ahead of the annual August event. Several restaurants, pubs, and private clubs including Soho House and UK pub chain Wetherspoons have also prohibited - or strongly discouraged - patrons from wearing these types of smart glasses in their establishments, citing privacy concerns. Apart from CCTV cameras, “the general code that applies in our pubs, and most pubs, is that you can't film customers or employees without their permission,” a Wetherspoons spokesperson previously told The Register. “Meta glasses seem to breach this code, and common sense, by enabling surreptitious surveillance, so our instinct is to say turn off the cameras.” Some National Basketball Association arenas have also reportedly told fans to go put their glasses with recording capabilities inside their vehicles and not wear them at NBA games. Meanwhile, the UK's privacy watchdog in March began investigating Meta's smart glasses after reports that human contractors reviewing recordings from the devices were exposed to extremely private moments captured by unsuspecting users. ®

Surveillance tech company Flock has struggled with its public image for years, but the problem has become particularly acute in recent weeks. Its network of ALPRs has long attracted criticism over mass surveillance and the retention of location data belonging to motorists who are not suspected of any offense. Days after its CEO apologized for documented abuses of the company's system, The Register contacted the company's usually responsive media team about an online campaign calling for its automated license plate readers (ALPRs) to be vandalized on Halloween, and received an automated response. "Thanks for reaching out to Flock. Our media team is currently touching grass and taking a break," the email said. "Unlike our cameras, we can't work 24/7, so we'll get back to you when we've had a snack and regained the ability to form coherent sentences." The media handlers have a lot on their plate. More recently, reports of ICE agents accessing local police forces' Flock systems, and police officers using the technology to stalk former partners, have coincided with an increase in vandalism targeting the cameras. This week, US social media users began promoting Halloween 2026 as a night of action against Flock's ALPRs, which continue to attract negative coverage. X grouped posts about the so-called "De-Flock America" campaign into a dedicated trending story, which recorded more than 36,500 posts over two days. Similar calls have appeared on other major social platforms. Posts encourage participants to wear costumes, leave their smartphones at home, and disable nearby ALPRs while concealing their identities. The Reg asked Flock whether it was aware of the campaign and planned any countermeasures, but received only the automated response. Apologies and changes Last week, Flock CEO Garrett Langley apologized after a woman was stalked using his company's ALPR system. "It kills me that she went through that," he told CBS News in an interview, less than two weeks after The Washington Post published a story highlighting 46 cases involving US police officers abusing their access to Flock's system. Some allegedly involved officers abusing that power to stalk women. Langley gave the interview after Flock announced an array of changes, including reducing its standard data retention period from 30 days to seven. Customers may retain information for longer, however. A new "Evidence Mode" allows law enforcement to retain data beyond that seven-day period if it's required for ongoing casework. Flock also introduced controls allowing police agencies to restrict the types of searches that outside forces can run against their data. For example, City A might request permission to search data belonging to City B as part of an investigation. With the new feature, City B can restrict City A from making searches related to "immigration enforcement," a nod to ICE agents accessing police Flock systems without a dedicated contract. Flock will also require customers to enable its existing Audit Assistance feature by year-end. The tool detects unusual search activity and flags it for review. It is currently optional but will become mandatory by year-end, having been "associated with arrests of several law enforcement officers who allegedly abused the system." Flock said more than a third of customers have voluntarily opted in to Audit Assistance so far. Langley's interview appeared one day after People reported that Haines City police officer Christopher Goodson, 31, allegedly used Flock to search for his estranged wife's license plate 717 times. The searches took place between September 1, 2024, and June 30, 2026, according to a probable cause affidavit. Goodson was suspended with pay pending further investigation. ®