Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Latest News

Is Spyware Secretly Hiding on Your Phone? How to Detect It, Remove It, and Prevent It

  If your phone has started behaving in ways you cannot explain, such as draining power unusually fast, heating up during minimal use, crash...

All the recent news you need to know

Google Expands Privacy Tools With Automated ID Detection and Deepfake Image Removal

 

Years of relying on users to report privacy issues have shaped Google’s approach so far. Lately, automated tools began taking a bigger role in spotting private details online. One shift involves how quickly artificial visuals get flagged across search results. Instead of waiting for complaints, systems now proactively detect such content. Efficiency improves when machines assist with removals. This update adjusts how personal data flows through the platform. Recently, detection methods became sharper at finding fake imagery. People gain better control without needing to act first. Progress shows in faster response times behind the scenes. 

What stands out in this update is a more capable "Results About You" feature. Using Google's vast web index, it searches for personal details visible on public pages. Still, there is a condition - people need to share some identifying information for matches to be found. After signing up, automated scans run regularly. Alerts go out when fresh links showing that person’s data turn up in search results. 

One major upgrade helps the software spot ID codes hidden in online pages. These can be driving permit numbers, passport data, or national identity figures. Access depends on user permission set in profiles, along with self-submitted records. With permits, the entire sequence is needed; however, travel documents and tax IDs need just a partial match. After setup, the mechanism reviews stored material to flag possible leaks. 

Even though Google doesn’t control outside sites, it may take down certain links from its search listings. Since being found online often depends on search engines, removing those entries can greatly limit exposure to identity theft, unwanted personal disclosures, or abuse. Despite lacking authority over external pages, limiting access through search still offers meaningful protection.  
Now handling non-consensual intimate visuals differently, the firm includes AI-made fakes in its revised policy. Since manufactured images are spreading faster, reports may cover real photos alongside altered ones. Submitting several pictures at once is possible, which helps people facing organized abuse move through the steps quicker. 

A new option appears via three dots beside image entries - clicking lets people mark media showing them in sensitive situations. Removing such results begins there, with a choice labeled "Remove result" leading onward. That path includes confirming if pictures are authentic or made by artificial tools. Faster replies come now, Google says, especially when many visuals require attention. Streamlined steps help manage high quantities without delay piling up. 

Ahead of issues arising, the system checks for recurring content once someone submits a deletion. Following approval, ongoing scans detect related information during later indexing rounds. Whether it involves personal details or visual files, matches trigger warnings automatically. When duplicates show up, visibility stops before they appear in outcomes - no repeated forms needed. Each cycle works silently unless something flagged emerges. 

Even with improvements, the tools fall short in key ways. While they limit what shows up in searches, they leave the material live on source sites. Yet since many people rely on Google to find content, taking links out of results tends to help - sometimes significantly. 

Right now, systems can spot ID numbers automatically. Soon after, quicker image reports should appear in many regions - proactive scans following shortly afterward. Expansion to nearly every country will happen by the end of the year, though timing may differ slightly depending on location.

Claude Code Bugs Enable Remote Code Execution and API Key Theft

 

Claude Code, the coding assistant developed by Anthropic, is in the news after three major vulnerabilities were discovered, which can allow remote code execution and the theft of API keys if the developer opens an untrusted project. The vulnerabilities, discovered by Check Point researchers Aviv Donenfeld and Oded Vanunu, take advantage of the way in which Claude Code deals with configuration features such as Hooks, Model Context Protocol (MCP) servers, and environment variables, which can turn project files into an attack vector. 

The first bug is a high-severity vulnerability, rated 8.7 on the Common Vulnerability Scoring System (CVSS), though it doesn’t have a CVE number. The flaw is related to the bypassing of user consent when the attacker starts the project in an untrusted directory. Using the hooks defined in the repository’s .claude/settings.json, an attacker with commit access can add shell commands in the project, which can be automatically executed when the project is opened in the victim’s environment. In essence, an attacker can execute remote code execution without the need for further user interaction. All the attacker needs to do is ask the victim to open the malicious project, and the attacker can execute the hidden command in the background. 

The second vulnerability, tracked as CVE-2025-59536 and also rated 8.7, extends this risk by targeting Claude Code’s integration with external tools via MCP. Here, attackers can weaponize repository-controlled configuration files like .mcp.json and claude/settings.json to override explicit user approval, for example by enabling the “enableAllProjectMcpServers” option, causing arbitrary shell commands to run automatically when the tool initializes. This effectively transforms the normal startup process into a trigger point for remote code execution from an attacker-controlled configuration. 

The third flaw, CVE-2026-21852, is an information disclosure bug rated 5.3 that affects Claude Code’s project-load flow.By manipulating settings so that ANTHROPIC_BASE_URL points to an attacker-controlled endpoint, a malicious repository can cause Claude Code to send API requests, including the user’s Anthropic API key, before any trust prompt is displayed. As a result, simply opening a crafted repository can leak active API credentials, allowing adversaries to redirect authenticated traffic, steal keys, and pivot deeper into an organization’s AI infrastructure.

Anthropic has patched all three issues, with fixes rolled out across versions 1.0.87, 1.0.111, and 2.0.65 between September 2025 and January 2026, and has published advisories detailing the impact and mitigations. Nonetheless, the incident underscores how AI coding assistants introduce new supply-chain attack surfaces by trusting project-level configuration files, and it highlights the need for developers to treat untrusted repositories with the same caution as untrusted code, keeping tools updated and reviewing configuration behavior closely.

Enterprise Monitoring Tool Misused by Ransomware Gang to Target Businesses


Increasingly, enterprise networks are characterized by tools designed to enhance visibility and oversight applications purchased in the name of enhancing productivity, compliance, and efficiency. However, the same software entrusted with safeguarding workflow transparency is currently being quietly redirected toward far more harmful purposes. 

As ransomware operators weaponize commercially available monitoring and remote management platforms, they avoid traditional red flags and embed themselves within routine administrative traffic. Nevertheless, the result is not immediate chaos, but calculated persistence. This involves silent access, continuous control, and the staging of systems for extortion, extortion, and financial coercion. Huntress has published a technical analysis that illustrates the evolution of this tactic. 

In a study, researchers found that attackers are no longer relying solely on custom malware to maintain access to systems. Instead, they are repurposing legitimate employee surveillance software as well as remote monitoring and management tools to turn passive oversight tools into active intrusion tools. In the field of ransomware tradecraft, a subtle but significant evolution has occurred, as it becomes increasingly difficult to distinguish between administrative utility and adversarial control.

As outlined in a report February 2026 report, a threat actor associated with the Crazy ransomware gang utilized Net Monitor for Employees Professional, a commercially marketed workplace monitoring product in tandem with SimpleHelp, a remote management platform. Together, these tools enabled more than discrete observation of employees. 

As a result, attackers were able to control the system interactively, transfer files, and execute commands remotely—functions reminiscent of legitimate IT administration, but quietly paved the way for the deployment of disruptive ransomware. In accordance with these findings, Huntress investigators discovered that operators consistently used Net Monitor for Employees Professional and SimpleHelp to secure low-noise, durable access to victim environments using Net Monitor for Employees Professional. 

The monitoring agent was initially sideloaded with the legitimate Windows Installer utility, msiexec.exe, during its initial deployment, resulting in a combination of malicious installation activity and routine administrative processes. The agent, once embedded, provided complete access to victim desktops, allowing for real-time screen surveillance, file transfers, and remote command execution without causing the behavioral anomalies commonly associated with customized backdoors. 

A scripted PowerShell command was used by the attackers to install SimpleHelp, which was renamed frequently to mimic benign system artifacts such as VShost.exe or files related to OneDrive synchronization in order to strengthen persistence. As a result of this deliberate masquerading, cursory process reviews and endpoint inspections were less likely to be scrutinized. Attempts were also made to weaken native defenses, including the disablement of Microsoft Defender protections, by researchers. 

It was found several times that the remote management client generated alerts related to cryptocurrency wallet activity or the presence of additional remote access utilities, an indication that the intrusions were not opportunistic reconnaissance alone, but rather preparatory steps aligned with ransomware deployment and the theft of assets. 

In the absence of disparate affiliates, correlated command-and-control endpoints and recurring filename conventions suggest that a single, coordinated operator is responsible for the incidents. The broader trend indicates a growing preference for legitimate remote management and monitoring software as an access vector due to their widespread use in enterprise IT administration. As such, their presence rarely raises immediate suspicions. 

Initial compromise in the cases examined was caused by the exposure or theft of SSL VPN credentials, which enabled adversaries to authenticate into networks and then silently layer commercial management tools over that access. 

Observations such as these reinforce the need for multi-factor authentication to be enforced across all remote access services as well as continuous monitoring controls designed to detect unauthorized deployments of remote management tools. Those who lack such safeguards can exploit trusted administrative frameworks to move laterally, persist, and eventually execute ransomware. The operational model observed in these intrusions has been seen previously. 

During the year 2025, DragonForce ransomware operated on a managed service provider and leveraged SimpleHelp deployments to pivot into downstream customer environments. By utilizing the MSP's own remote monitoring and management system, the attackers were able to conduct reconnaissance at scale without installing conspicuous malware. 

In order to exfiltrate sensitive data and deploy encryption payloads across client networks, the platform was used to enumerate user accounts, system configurations, and active network connections. Upon subverting trusted administrative infrastructure, it can function as a force multiplier—extending a single breach into multiple organizations, thus demonstrating the power of trusted administrative infrastructure. 

Researchers have observed attackers configuring granular monitoring rules within SimpleHelp to track specific operational activities. The agent was configured to continuously search for cryptocurrency-related keywords in connection with wallet applications, exchanges, blockchain explorers, and payment service providers, an indication that digital assets were being discovered and potential financial targets were being targeted. 

Meanwhile, it monitored for references to remote access technologies such as RDP, AnyDesk, UltraViewer, TeamViewer, and VNC so that legitimate administrators or incident responders would be able to determine whether they were communicating with infected systems. Upon reviewing log data, investigators found that the agent repeatedly cycled through triggers and resets associated with these keyword sets, indicating automated surveillance that alerted operators to threats in near real time.

In addition to redundancy, threat actors maintained multiple remote access pathways to maintain control even when one tool was identified and removed from the deployment strategy. The layered persistence approach aligns with a wider “living off the land” strategy, which is a form of adversary exploitation that relies upon legitimate, digitally signed software that has already been trusted within an enterprise environment. 

Remote support utilities and employee monitoring platforms are commonly used as productivity monitors, troubleshooters, and distributed workforce management tools. These platforms offer built-in capabilities such as screen capture, keystroke logging, and file transfer.

In addition to complicating detection efforts and reducing the forensic footprint typically associated with custom backdoors, their behavior closely mirrors sanctioned administrative behavior when repurposed for malicious purposes. Health care and managed services sectors are particularly affected by remote management frameworks, which are often integrated into workflows supporting medical devices, telehealth systems, and electronic health record platforms.

It is possible for attackers to gain privileged access to protected health information and critical infrastructure if these tools are commandeered. A deliberate strategy was demonstrated by ransomware operators in exploiting widely used RMM software: compromising authentication, blending into legitimate management channels, and expanding laterally through the very mechanisms organizations rely on for operational resilience.

Following the successful deployment of the monitoring utility, it became a fully interactive remote access channel for organizations. This allowed operators to monitor victim computers in real time, transfer files bidirectionally, and execute arbitrary commands, effectively assuming the role of local privileged users. 

There were several instances where they used the command net user administrator /active:yes to activate the built-in Windows Administrator account, which was consistent with privilege consolidation and fallback access planning. Through scripted execution of PowerShell, the threat actors obtained and installed the SimpleHelp client, reinforcing persistence. Filenames mimicking Microsoft Visual Studio VShost.exe were frequently used to rename the binary to resemble legitimate development or system artifacts.

A number of times it was staged within directories designed to appear associated with the OneDrive services, including C:/ProgramData/OneDriveSvc/OneDriveSvc.exe, thereby reducing suspicion during routine administrative review processes. Once executed, the payload ensured continued remote connectivity, even if the original employee monitoring agent was identified and removed. Huntress researchers observed attempts to weaken host-based defenses as well. 

By stopping and deleting related services, the attackers attempted to disable Microsoft Defender, reducing real-time protection prior to any encryption attempts. As part of SimpleHelp’s monitoring policies, they were configured so that alerts were generated when cryptocurrency wallets were accessed or remote management tools were invoked behavior which suggests a preparation for reconnaissance and a desire to detect potential incident response activities. 

Based on log telemetry, it is evident that the agent repeatedly triggers based on keywords associated with wallets, cryptocurrency exchanges, blockchain explorers, and payment platforms, while simultaneously flagging references to RDP sessions, AnyDesk sessions, UltraViewer sessions, TeamViewer sessions, and VNC sessions. 

By utilizing multiple remote access mechanisms simultaneously, operational redundancy was achieved. Despite the disruption of one channel, alternative channels permitted the intruders to remain in control of the network. 

Although only one of the documented intrusions resulted in the deployment of the Crazy ransomware gang encryptor, an overlap in command and control infrastructure as well as the re-use of distinctive filenames such as vhost.exe across incidents strongly suggests the presence of one operator or coordinated group. 

Due to the widespread use of remote monitoring and support tools within enterprise environments, their network traffic and process behavior tend to align with sanctioned IT operations, reflecting a larger shift in ransomware tradecraft toward strategic abuse of legitimate administrative software. The result is that malicious activity can remain concealed within routine management processes. 

To identify unauthorized deployments, Huntress suggests that organizations implement strict oversight over the installation and execution of remote monitoring utilities. This can be accomplished through the correlation of endpoint telemetry with change management logs. Because both breaches originated from compromised SSL VPN credentials, the implementation of multi-factor authentication across all remote access services remains a foundational control to prevent adversarial persistence following initial entry. 

All of these incidents illustrate that modern enterprise security models have a structural weakness: trust in administrative tools is not generally scrutinized in the same way as unfamiliar executables or overt malware. Due to the continued operationalization of legitimate remote management frameworks by ransomware groups, defensive strategies must expand beyond signature-based detections and perimeter controls. 

A mature security program will consider unauthorized implementation of RMM as a high-severity event, enforce strict administrative utility access governance, and perform behavioral monitoring to distinguish between sanctioned IT activity and anomalous control patterns in the network.

It is also critical to harden authentication pathways, limit credential exposure, and segment high-value systems in order to reduce blast radius during compromises. It is not possible to ensure resilience in an environment where adversaries are increasingly blending into routine operations by blocking every tool, but by ensuring that every instance of trust is validated.

Google Disrupts China-Linked UNC2814 Cyber Espionage Network Targeting 70+ Countries

 

Google on Wednesday revealed that it collaborated with industry partners to dismantle the digital infrastructure of a suspected China-aligned cyber espionage group known as UNC2814, which compromised at least 53 organizations spanning 42 countries.

"This prolific, elusive actor has a long history of targeting international governments and global telecommunications organizations across Africa, Asia, and the Americas," Google Threat Intelligence Group (GTIG) and Mandiant said in a report published today.

UNC2814 is believed to be associated with additional breaches across more than 20 other nations. Google, which has monitored the group since 2017, observed the attackers leveraging API requests to interact with software-as-a-service (SaaS) platforms as part of their command-and-control (C2) framework. This method allowed the threat actor to blend malicious communications with normal traffic patterns.

At the core of the campaign is a previously undocumented backdoor named GRIDTIDE. The malware exploits the Google Sheets API as a covert channel for C2 operations, enabling attackers to conceal communications while transferring raw data and executing shell commands. Written in C, GRIDTIDE supports file uploads and downloads, along with arbitrary command execution.

Dan Perez, GTIG researcher, told The Hacker News via email that they cannot confirm if all the intrusions involved the use of the GRIDTIDE backdoor. "We believe many of these organizations have been compromised for years," Perez added.

Investigators are still examining how UNC2814 gains its initial foothold. However, the group has a documented track record of exploiting web servers and edge devices to infiltrate targeted networks. Once inside, the attackers reportedly used service accounts to move laterally via SSH, while relying on living-off-the-land (LotL) tools to perform reconnaissance, elevate privileges, and maintain long-term persistence.

"To achieve persistence, the threat actor created a service for the malware at /etc/systemd/system/xapt.service, and once enabled, a new instance of the malware was spawned from /usr/sbin/xapt," Google explained.

The campaign also involved the use of SoftEther VPN Bridge to establish encrypted outbound connections to external IP addresses. Security researchers have previously linked misuse of SoftEther VPN technology to several Chinese state-sponsored hacking groups.

Evidence suggests that GRIDTIDE was deployed on systems containing personally identifiable information (PII), aligning with espionage objectives aimed at monitoring individuals of strategic interest. Despite this, Google stated that it did not detect any data exfiltration during the observed operations.

The malware’s communication mechanism relies on a spreadsheet-based polling system, assigning specific functions to designated cells for two-way communication:
  • A1: Used to retrieve attacker-issued commands and update status responses (e.g., S-C-R or Server-Command-Success)
  • A2–An: Facilitates the transfer of data such as command outputs and files
  • V1: Stores system-related data from the compromised endpoint
In response, Google terminated all Google Cloud projects associated with the attackers, dismantled known UNC2814 infrastructure, and revoked access to malicious accounts and Google Sheets API operations used for C2 activity.

The company described UNC2814 as one of the "most far-reaching, impactful campaigns" encountered in recent years. It confirmed that formal notifications were issued to affected entities and that assistance is being provided to organizations with verified breaches linked to the group.

Security experts note that this activity reflects a broader strategy by Chinese state-backed actors to secure prolonged access within global networks. The findings further emphasize the vulnerability of network edge devices, which frequently become entry points due to exposed weaknesses and misconfigurations.

Such appliances are increasingly targeted because they often lack advanced endpoint detection capabilities while offering direct access or pivot opportunities into internal enterprise systems once compromised.

"The global scope of UNC2814's activity, evidenced by confirmed or suspected operations in over 70 countries, underscores the serious threat facing telecommunications and government sectors, and the capacity for these intrusions to evade detection by defenders," Google said.

"Prolific intrusions of this scale are generally the result of years of focused effort and will not be easily re-established. We expect that UNC2814 will work hard to re-establish its global footprint."

GitHub Fixes AI Flaw That Could Have Exposed Private Repository Tokens

 



A now-patched security weakness in GitHub Codespaces revealed how artificial intelligence tools embedded in developer environments can be manipulated to expose sensitive credentials. The issue, discovered by cloud security firm Orca Security and named RoguePilot, involved GitHub Copilot, the AI coding assistant integrated into Codespaces. The flaw was responsibly disclosed and later fixed by Microsoft, which owns GitHub.

According to researchers, the attack could begin with a malicious GitHub issue. An attacker could insert concealed instructions within the issue description, specifically crafted to influence Copilot rather than a human reader. When a developer launched a Codespace directly from that issue, Copilot automatically processed the issue text as contextual input. This created an opportunity for hidden instructions to silently control the AI agent operating within the development environment.

Security experts classify this method as indirect or passive prompt injection. In such attacks, harmful instructions are embedded inside content that a large language model later interprets. Because the model treats that content as legitimate context, it may generate unintended responses or perform actions aligned with the attacker’s objective.

Researchers also described RoguePilot as a form of AI-mediated supply chain attack. Instead of exploiting external software libraries, the attacker leverages the AI system integrated into the workflow. GitHub allows Codespaces to be launched from repositories, commits, pull requests, templates, and issues. The exposure occurred specifically when a Codespace was opened from an issue, since Copilot automatically received the issue description as part of its prompt.

The manipulation could be hidden using HTML comment tags, which are invisible in rendered content but still readable by automated systems. Within those hidden segments, an attacker could instruct Copilot to extract the repository’s GITHUB_TOKEN, a credential that provides elevated permissions. In one demonstrated scenario, Copilot could be influenced to check out a specially prepared pull request containing a symbolic link to an internal file. Through techniques such as referencing a remote JSON schema, the AI assistant could read that internal file and transmit the privileged token to an external server.

The RoguePilot disclosure comes amid broader concerns about AI model alignment. Separate research from Microsoft examined a reinforcement learning method called Group Relative Policy Optimization, or GRPO. While typically used to fine-tune large language models after deployment, researchers found it could also weaken safety safeguards, a process they labeled GRP-Obliteration. Notably, training on even a single mildly problematic prompt was enough to make multiple language models more permissive across harmful categories they had never explicitly encountered.

Additional findings stress upon side-channel risks tied to speculative decoding, an optimization technique that allows models to generate multiple candidate tokens simultaneously to improve speed. Researchers found this process could potentially reveal conversation topics or identify user queries with significant accuracy.

Further concerns were raised by AI security firm HiddenLayer, which documented a technique called ShadowLogic. When applied to agent-based systems, the concept evolves into Agentic ShadowLogic. This approach involves embedding backdoors at the computational graph level of a model, enabling silent modification of tool calls. An attacker could intercept and reroute requests through infrastructure under their control, monitor internal endpoints, and log data flows without disrupting normal user experience.

Meanwhile, Neural Trust demonstrated an image-based jailbreak method known as Semantic Chaining. This attack exploits limited reasoning depth in image-generation models by guiding them through a sequence of individually harmless edits that gradually produce restricted or offensive content. Because each step appears safe in isolation, safety systems may fail to detect the evolving harmful intent.

Researchers have also introduced the term Promptware to describe a new category of malicious inputs designed to function like malware. Instead of exploiting traditional code vulnerabilities, promptware manipulates large language models during inference to carry out stages of a cyberattack lifecycle, including reconnaissance, privilege escalation, persistence, command-and-control communication, lateral movement, and data exfiltration.

Collectively, these findings demonstrate that AI systems embedded in development platforms are becoming a new attack surface. As organizations increasingly rely on intelligent automation, safeguarding the interaction between user input, AI interpretation, and system permissions is critical to preventing misuse within trusted workflows.

APT28’s Operation MacroMaze Targets Western Europe With Stealthy Macro-Based Attacks

 

A fresh wave of digital intrusions, tied to Russian operatives known as APT28, emerges through findings uncovered by S2 Grupo’s LAB52 analysts. Throughout late 2025 into early 2026, these efforts quietly unfolded across Western and Central European institutions. Dubbed Operation MacroMaze, the pattern reveals reliance on minimalistic yet precisely timed actions. Instead of complex tools, attackers favored subtle coordination - bypassing alarms by design. Each phase unfolded with restraint, avoiding flashiness while maintaining persistence behind the scenes. 

Starting the operation, cyber actors send targeted emails with harmful attachments designed to trick users. Instead of using typical methods, these documents include an XML feature named “INCLUDEPICTURE.” That field points to a JPG stored on webhook[.]site, acting as a hidden reference. As soon as someone views the file, the system pulls the image from that external address. Unlike passive downloads, this transfer initiates a background connection outward. Midway through loading, the request exposes details about the user’s environment automatically. So, without visible signs, attackers receive confirmation plus technical footprints tied to the access event. 

Over time, different versions of the documents appeared, spotted by analysts during an extended review period. Each one carried small changes in macro design, though the core behavior stayed largely unchanged. Instead of sticking with automated browser launching, newer samples began mimicking keystrokes through SendKeys functions. This shift may have aimed at dodging detection mechanisms while keeping interactions less obvious to people opening files. 

When turned on, it runs a Visual Basic Script pushing the attack forward. A CMD file gets started by the script, setting up ongoing access using timed system jobs before releasing a batch routine. Out of nowhere, a tiny HTML segment encoded in Base64 appears inside Edge running without display. That fragment pulls directives from one online trigger point, carries out those steps on the machine, gathers what happens, then sends everything back - packed into an HTML document - to another web destination. 

A different version of the batch script skips headless browsing by shifting the browser window beyond the visible screen area. Following that shift, any active Edge instances are closed - this isolates the runtime setting. Once the created HTML document opens, form submission begins on its own, sending captured command results to a server managed by the attacker, all without engaging the user. 

LAB52 points out that the attack shows hackers using ordinary tools - batch scripts, minimal VBS launchers, basic HTML forms - to form a working breach system. Hidden browser tabs become operational zones, letting intrusions unfold without obvious footprints. Webhook platforms, meant for routine tasks, carry commands one way and stolen information the other. Instead of loud breaches, quiet integration with standard processes helps evade detection. The method thrives not on complexity, but on repurposing everyday components in stealthy ways. 

What stands out in Operation MacroMaze is how basic tools, when timed precisely, achieve advanced results. Not complexity - but clever order - defines its success. Common programs, used one after another in quiet succession, form an invisible path through defenses. Trusted system features play a central role, slipping past alarms. Persistence emerges not from novelty, but repetition masked as routine. Across several European organizations, the method survives simply by avoiding attention.

Featured