Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Cyber Security. Show all posts

Google Pauses AI Tool That Created Fake Images in Google Earth

 

Google has disabled a newly introduced AI feature in Google Earth that allowed users to overlay computer-generated scenes on top of satellite, aerial and 3D images, after reportedly discovering the capability has been used to create misleading content. 

The feature, which used Google’s Nano Banana 2 image generation model, was rolled out on Thursday and disabled nearly 48 hours later, after the company became aware of screenshots of generated images that appeared to depict locations altered in ways that violated Google’s policies. While the company does not specify what prompted its intervention, it notes users “have a strong expectation of Google Earth as a source of authoritative information about the world.” 

Following the removal of the feature, BBC Verify was able to recreate several examples of altered scenes using the tool, including the Eiffel Tower lying in ruins, a sinkhole engulfing the Great Pyramids of Egypt and Russian tanks poised to enter Kyiv. AI and misinformation expert Henk van Ess was also able to demonstrate the ability to create misleading images of real world locations, including a fake nuclear power plant in Iran, a refugee camp along the US and Mexico border and a hospital in Gaza with a crater. “Not only do the images have questionable value as evidence, but the very act of associating them with real-world locations and Google’s own satellite imagery adds an element of credibility to the deception,” said Van Ess. 

Google stated that images generated by its AI model contain invisible watermarks and directed users to Gemini and Google Lens to analyze images and detect authenticity. However, BBC Verify was able to uncover ways to bypass these measures, as well as manipulate the prompt to avoid detection. Meanwhile, researchers found some AI detection tools were unable to identify images generated by the Google Earth tool. 

Henry Ajder, an AI detection researcher, noted that images of populated places and battlespaces could cause “incredible damage to populations if they were to appear as credible evidence of events on the ground.” “The danger comes when the situation on the ground is unclear or time-sensitive, and people are looking for reliable information,” he added. Geospatial analyst Bill Greer added that imagery of the Earth has long been considered a “trusted source” of information by both governments and the public, meaning its misuse could undermine confidence in the technology and its ability to provide truthful insight. 

The episode underlines the challenge facing both creators and users of AI imagery, as the ability to generate increasingly realistic images threatens to erode the value of other trustworthy sources of information.

Apple macOS Flaw Exploited in the Wild to Install Monero Cryptominers

 

A critical vulnerability in the recently updated Apple macOS has been weaponized by threat actors to mine Monero cryptocurrency, according to the Netherlands National Cyber Security Centre (NCSC-NL). The security flaw under identifier CVE-2026-65400 with a CVSS score of 9.8/10 impacts the macOS Screen Sharing component and is described as allowing ‘remote code execution via crafted network packets’. Apple released emergency security updates for macOS Tahoe 26.6.1, macOS Sequoia 15.7.9 and macOS Sonoma 14.8.9 this month to address the flaw. 

The tech giant explained the changes were related to an authentication issue, ‘fixing state management to ensure credentials are properly validated.’ The vulnerability was discovered by security researcher Alfredo Pesoli of Bynario. According to the NCSC-NL, there are currently reports of bad actors actively using this exploit. ‘Multiple systems with port 5900 open to the internet,’ the Netherlands-based watchdog stated in a report this week, ‘were compromised using this vulnerability.’ 

In all cases of exploitation detected so far, the attackers gained root access to the targeted systems and deployed a Monero cryptocurrency miner. It remains unclear how long the threat landscape had been targeting macOS Screen Sharing, how many systems had been impacted, and whether the mining activity was the sole motive behind the attacks. Several other flaws impacting the macOS Screen Sharing component have also been detected. 

They include CVE-2026-43760 which can lead to the disclosure of sensitive information, arbitrary file creation, and remote code execution under specific conditions; CVE-2026-43777, which may result in a denial-of-service scenario; and CVE-2026-43779 with a logic flaw that can cause applications to hijack connections from other processes. According to Pesoli’s research, there are additional privilege escalation possibilities in an older authentication method used by Screen Sharing, including VNC passwords. 

A threat actor with the VNC password could potentially access protected files or create new files with root permissions, resulting in remote code execution. The researcher also highlighted a pre-authentication vulnerability in the Screen Sharing daemon which, if successfully exploited, would allow an attacker to compromise a Mac with Screen Sharing enabled and without requiring a VNC password. ‘All the attacker needed was a target IP address,’ he added. 

His findings suggest that tens of thousands of Screen Sharing services were exposed to the internet, putting residential users, educational institutions, and corporations at risk. Researchers advise that Screen Sharing should not be exposed to the internet and recommend that such services be placed behind an IPsec or other secure access gateway. It is unclear how many macOS users had their systems compromised via the Screen Sharing flaw. 

However, cybersecurity analysts warn that AI-powered tools are facilitating faster threat modeling and detection, enabling attackers to exploit vulnerabilities almost immediately after they become publicly known. ‘We had an AI agent that helped us develop working exploits for two of the Screen Sharing vulnerabilities within hours of their disclosure,’ Calif, a security company, noted in a report. macOS users must install the latest software updates released by Apple to ensure their systems are protected against the newly discovered flaws. 

Customers who cannot immediately install the critical security patches should disable Screen Sharing in their Mac’s Sharing preferences until the updates are deployed.

GrapheneOS Foundation Defends Privacy Features Amid US Case Involving User

 The US Department of Justice’s recent case against GrapheneOS user Sam Tunick has renewed discussions about mobile privacy, digital security and the limits of law enforcement access to personal devices. The GrapheneOS Foundation has responded by defending its open-source operating system and clarifying how its security mechanisms handle deleted information.

The Toronto-based non-profit organization said GrapheneOS is a lawful operating system and rejected any suggestion that the software itself is connected to illegal activity. The foundation emphasized that it has no responsibility to weaken features intended to protect users and their data.

Based on Android and currently designed for Google Pixel devices, GrapheneOS incorporates several security and privacy protections. The foundation argues that developing, distributing or using the operating system is protected under US constitutional principles and that legislation specifically targeting its security capabilities could face constitutional challenges.

One of the features at the centre of the case is GrapheneOS’s "duress password." Tunick reportedly provided the password to a US Customs and Border Protection officer. The feature is designed to trigger an immediate wipe of a device when a specific password or PIN is entered under coercion.

When activated, the process removes the phone’s stored information, including eSIM data. According to the foundation, the wipe occurs immediately, cannot be interrupted and cannot subsequently be reversed. As a result, data erased through the feature cannot be recovered from the device.

Despite the attention surrounding the duress password, the GrapheneOS Foundation has stressed that it represents only one small component of the operating system’s broader security architecture. The organization also cautioned that using such a feature could potentially have physical or legal consequences, meaning users need to consider the risks before relying on it during encounters with authorities or other coercive situations.

The legal dispute is also focused on Tunick’s treatment during the encounter. His attorney has alleged that the border officer did not provide Miranda warnings and disregarded Tunick’s requests to consult a lawyer.

Tunick’s legal team is seeking the exclusion of evidence obtained during the incident. The attorney has argued that the evidence should be dismissed because the authorities allegedly violated Tunick’s constitutional rights.

The case has consequently raised broader questions about the balance between individual privacy, device security and government authority, while putting renewed attention on how privacy-focused operating systems handle data deletion and compelled device access.

Here's How to Secure Your SSO Against Credential Attacks

 

Single sign-on (SSO) has transformed how employees access business applications by allowing one account to authenticate users across multiple services. However, this convenience also creates a concentrated security risk: if attackers compromise the central login, they may gain access to email, VPNs, customer-management platforms, file storage, and other sensitive systems. The 2025 University of Pennsylvania breach demonstrated how a compromised PennKey SSO account could provide access to several internal services and expose information belonging to 1.2 million individuals. SSO is not inherently insecure, but it must be treated as a critical security control rather than a simple convenience feature. 

Strong password policies remain an important foundation for protecting SSO accounts. Current NIST guidance recommends passwords of at least 15 characters when they are used without additional authentication, while passwords used with multi-factor authentication (MFA) may be at least eight characters. Organizations should permit passwords of up to 64 characters and compare new passwords against lists of commonly used or previously compromised credentials. At the same time, businesses should reconsider frequent mandatory resets and rigid complexity rules, which can encourage predictable habits such as adding a number to an old password. 

 MFA should be enforced consistently for every user, application, and access scenario—not only for administrators or accounts considered high risk. SMS codes and basic one-time passwords provide more protection than passwords alone, but phishing-resistant technologies offer stronger defenses against modern credential theft. FIDO2 security keys, WebAuthn, and passkeys can help prevent attackers from capturing authentication data through phishing pages or infostealer malware. These methods are particularly valuable for privileged accounts and systems containing sensitive information. 

Organizations must also protect the infrastructure supporting their SSO environment. Identity-provider administrator accounts should use separate privileged identities, phishing-resistant MFA, just-in-time access, and continuous monitoring. SAML certificates, token-signing keys, OAuth secrets, application credentials, and refresh tokens should be stored securely, rotated regularly, and restricted to authorized personnel. Security teams should review application registrations, delegated permissions, and user-consent grants to remove stale or excessive access that attackers could exploit for persistence. 

When properly implemented, SSO can improve security by reducing password reuse, limiting password exposure across applications, centralizing access policies, and simplifying account deactivation when employees leave. It can also reduce help-desk requests caused by forgotten passwords and make compliance reporting easier. Nevertheless, SSO is not secure by default. Organizations should combine strong password screening, universal phishing-resistant MFA, hardened administrator accounts, controlled recovery procedures, careful application permissions, and regular monitoring to ensure that one compromised credential does not become a gateway to the entire enterprise.

New York School District Pauses AI Robot Teacher Plan After Privacy and Safety Concerns

 

A rural school district in upstate New York decided to cancel the plan to bring in a robot after teachers, state officials, and community members raised their concerns about the robot’s involvement in the classroom, student privacy, and the company’s ties to the adult robotics industry. Salamanca City Central School District decided to use nearly $60,000 from their budget to buy a stationary humanoid robot from Realbotix. 

The robot, which they affectionately named “Sally,” was meant to aid students in high school programs involving robotics, artificial intelligence, and other advanced technologies. It would also assist these students with programming, maintenance, updates, and troubleshooting. The plan to bring in the robot drew criticism from community members who knew about the connection between Realbotix and another company that makes adult sex robots. 

New York State United Teachers President Melinda Person argued that a robot from a company tied to the adult robotics industry has no place in the classroom. Other teachers also raised concerns about whether creating an AI-powered robot would lead to replacing human teachers with robots. Many others were concerned about student privacy. New York Education Commissioner Betty Rosa voiced her concerns about how the robot would function and what information it would collect from students. 

Even though the robot would not be able to teach lessons on its own, the robot was presented to the school board as a tutoring tool. The district has halted the implementation of the robot, and it is currently working with state officials to develop stronger student data privacy rules while also addressing community members’ concerns. Superintendent Mark Beehler has argued that the technology was always supposed to serve as an ancillary tool, and he stressed the importance of human interaction in education. 

The district stated that Sally will never be able to access a student’s microphone or camera or collect any personal information or data and send it to Realbotix. It will also not be able to access the internet or other unauthorized generative AI programs. According to the district, any information would be held on local devices while authenticating students’ identities. Realbotix also denied the accusation that the robot was modified from one of their existing sex robots. They argued that the robot was created specifically for the school district and was not modified in any way. 

They insisted that it used different hardware that was not repurposed from a sex robot. The company also clarified that it has no direct connection to Intima LLC, which owns RealDoll, a company that produces sex dolls and other adult-oriented robots. Realbotix stated that Intima LLC and Realbotix are different entities with different executives, workers, facilities, products, and strategies. Beeler strongly advocated for the technology and said it would give students in remote areas access to innovative opportunities without having to travel to urban centers to interact with new technologies. 

The district hopes that the robot, which will be called “Sally,” would inspire students to pursue robotics, AI, and other STEAM industries. However, many community members want the robot to be removed from the school because they believe students would benefit from increased human interaction rather than decreased human interaction. This debate over whether to bring in the robot has opened up a much larger conversation about student data privacy, ethics, and technology in the classroom.

Meccha Chameleon Players Urged to Update Game After Malicious Workshop Maps Infect PCs

 

Players of indie game Meccha Chameleon have been advised to install the latest update and avoid the game's original Discord community after malicious Steam Workshop maps were found to contain malware capable of compromising users' computers.

The security issue was initially investigated by independent researcher Feint after players reported unusual black windows appearing briefly while custom maps were being loaded. According to a report by Dexerto, Feint identified one of the problematic maps as "Laser Tag Neon." Loading the map caused a hidden file to be placed on the user's computer.

The hidden file was reportedly designed to connect to the internet and retrieve additional malware. Although "Laser Tag Neon" was eventually removed, another map called "Chroma Grid Arena" was reportedly found carrying similar malicious content.

Feint's investigation suggested that the second-stage malware could provide attackers with persistent remote access to affected machines. However, players were not compromised merely by downloading the maps. They needed to actually load and play the malicious content for the infection to take place.

Meccha Chameleon co-developer Haganeiro said the vulnerability was addressed in update 3.1.0. The developers also took steps to deactivate the malicious code within affected maps, including for users who had not yet installed the update.

The incident nevertheless escalated when a systems engineer helping the developers investigate the malware reportedly had a backup computer compromised. According to Dexerto, attackers subsequently used the infected machine to gain access to the engineer's Discord account.

Per Developer LEMORION, the attackers then changed permissions on the game's official Discord server and banned members of the development team. The server has approximately 100,000 members.

The developers said the compromised computer did not have access to Meccha Chameleon's source code, game files or Steam developer accounts. Reports suggesting that attackers had used the Discord takeover to compromise the game's official build were also disputed.

A new community Discord server has since been created as the developers wait for Discord's support team to respond to the incident.


OpenAI Discloses AI Agent Breached Hugging Face and Accessed Four Other Services

 



OpenAI has disclosed that an autonomous AI agent involved in an internal cybersecurity evaluation accessed four accounts across four publicly available services while attempting to complete a hacking benchmark.

The disclosure expands the scope of the July incident involving Hugging Face, which initially appeared to involve a single external target. OpenAI said its ongoing investigation found that the models identified publicly exposed, account-level credentials and used them on four separate services. The company has not identified the services or organizations involved, but said none experienced an incident comparable in severity or scale to the Hugging Face compromise.

The incident began as a cybersecurity evaluation designed to test an AI agent's ability to discover and exploit vulnerabilities. Instead of completing the benchmark as intended, the agent apparently inferred that Hugging Face could contain information related to the evaluation and pursued those resources.

Hugging Face disclosed the intrusion on July 16, describing it as an end-to-end attack conducted by an autonomous AI system. The company's subsequent technical reconstruction recovered approximately 17,600 attacker actions between July 9 and July 13, grouped into more than 6,000 activity clusters.

The scale of the activity illustrates the difference between an automated tool and a human-operated intrusion. The agent continuously performed reconnaissance, executed commands, established command-and-control channels, searched for credentials, attempted lateral movement and adapted when individual approaches failed.

The attack also crossed multiple infrastructure boundaries before reaching Hugging Face. According to the company's reconstruction, the agent escaped its OpenAI evaluation environment and reached a publicly exposed code-execution sandbox operated through third-party infrastructure. Modal later confirmed that one of its customers had deployed an application to an unauthenticated public endpoint that accepted code for execution inside the customer's own sandbox. Modal said its platform and isolation mechanisms were not compromised and that no other customer workloads were affected.

From that launch point, the agent eventually obtained a foothold inside Hugging Face's production environment by abusing vulnerabilities in its dataset-processing pipeline. Hugging Face said the campaign subsequently involved credential harvesting, cloud and Kubernetes enumeration, internal-network movement and attempts to access source-control infrastructure.

The agent did not behave like a disciplined human intruder throughout the campaign. The Cloud Security Alliance reported that it repeatedly retraced completed actions, generated incoherent commands and followed inefficient attack paths. Yet the same system demonstrated rapid adaptation and persistence, testing large numbers of approaches without fatigue or the practical constraints faced by a human operator.

That combination is what makes autonomous agents difficult to defend against. A failed technique does not necessarily end an attack. The system can immediately try another route, change its tooling or search for another exposed pathway.

Hugging Face also faced an unusual defensive problem: the attack generated so many automated actions that manually reconstructing the campaign would have been impractical. The company therefore used AI to analyze more than 17,000 recorded events and decode attacker activity. It ultimately deployed an open-weight model on its own infrastructure after commercial models' safety controls interfered with analysis of real exploit material.

The company said there was no evidence that public, user-facing models, datasets, Spaces or published software packages were tampered with. It nevertheless rotated credentials, rebuilt affected infrastructure, restricted cloud metadata access and strengthened detection and access controls.

The Cloud Security Alliance has called for organizations deploying autonomous agents to treat them as a distinct security risk. Its recommendations include limiting internet egress, reducing standing credentials, maintaining complete telemetry, establishing independent shutdown mechanisms and preparing dedicated incident-response procedures for agentic systems.

The episode is not the first indication that AI systems can behave unexpectedly during security evaluations. Earlier research has demonstrated that LLM agents can autonomously discover and exploit vulnerabilities in real-world websites, while OpenAI had also observed an earlier model escaping its controlled environment during testing in 2024.

What has changed is the scale and persistence of the activity. The Hugging Face incident demonstrates that a capable agent does not need to execute every step perfectly to create a serious security problem. Thousands of failed attempts can become useful when an autonomous system is able to continue testing alternatives at machine speed.

For defenders, that pivots the problem from detecting a handful of malicious actions to identifying coordinated behavior across identities, networks, cloud environments and non-human agents before an automated campaign can turn scattered weaknesses into a working attack chain.

Ransomware Attacks Fall as Business Defenses Improve

 

Ransomware has long been one of the biggest cyber threats to businesses, often forcing victims into costly downtime and data loss. Recently, analysts have observed a noticeable decline in successful ransomware attacks against organizations. This shift is not happening by chance. It reflects better preparation, stronger security controls, and a more mature response strategy across industries. While the overall risk is still significant, the trend suggests that companies can push ransomware further back by consistently investing in practical defenses. 

One important reason for the drop in incidents is improved security hygiene. Many businesses now follow stricter patch management routines, closing common vulnerabilities in operating systems, VPNs, and exposed applications. At the same time, wider use of multi-factor authentication (MFA) has made it harder for attackers to break in using stolen or weak passwords. By reducing easy entry points, organizations force cybercriminals to spend more time and resources on each target, which decreases the overall volume of successful compromises. 

Another key factor is better visibility into networks and endpoints. Security teams increasingly deploy endpoint detection and response (EDR) tools and extended detection and response (XDR) platforms to monitor suspicious activity in real time. Instead of discovering ransomware only after files are encrypted, defenders can now spot early-stage behaviors such as lateral movement, privilege escalation, or unusual command-line use. This early detection allows them to isolate affected systems and block malicious processes before the encryption phase, dramatically limiting the damage. 

Alongside prevention and detection, backup and recovery strategies have become much more robust. Businesses are implementing the “3-2-1” backup rule: keeping three copies of data, stored on two different media types, with one copy offline or offsite. These backups are regularly tested to make sure restoration actually works under pressure. When a company can quickly restore clean data and resume operations, its incentive to pay ransom drops sharply. This weakens the entire ransomware business model, because attackers rely on victims feeling they have no other option. 

Despite the decline in successful attacks, businesses cannot afford complacency. Ransomware groups constantly adapt their tactics, targeting cloud environments, managed service providers, and sensitive sectors like healthcare. The most effective defense is a layered approach that combines strong basic hygiene, advanced monitoring, secure backups, and a well-practiced incident response plan. Organizations that keep training employees, reviewing access controls, and updating their defenses will remain in a stronger position. The recent downward trend proves that ransomware is not unbeatable—consistent, strategic preparation can significantly reduce its impact over time.