CySecurity News - Latest Information Security and Hacking Incidents

CEO accountability cyberattack responsibility cybersecurity breaches Data Breach leadership

Debate Intensifies Over CEO Accountability in Cybersecurity Breaches

A growing debate is emerging around whether chief executives should be held directly accountable when companies suffer cyberattacks. Some experts argue that CEOs must face severe consequences, including automatic dismissal after a major breach, while others warn that such a policy could create dangerous incentives and worsen crisis management.

One viewpoint insists that cybersecurity failures are ultimately leadership failures. Security executives, according to this argument, often act as “bullet fodder” despite lacking control over budgets, risk appetite, or enforcement across business units. They can identify risks and recommend action, but final decisions rest with company leadership.

“CEOs should absolutely be held accountable for a cyberattack. In fact, I would go even further: when there’s a breach, defined as a system being compromised or data being stolen, the CEO should be automatically fired as a result.”

Supporters of stricter accountability say catastrophic breaches can damage customers, employees, supply chains, and the broader business ecosystem. When leadership underfunds security or ignores warnings, they argue, that is a deliberate business choice. They compare major cyber incidents to executive negligence in other corporate functions and suggest boards should establish predefined thresholds for breaches that automatically trigger CEO removal.

Another key point in this camp is incentives. Cyber resilience and risk reduction, advocates say, should be tied directly to executive compensation and employee bonuses so that cybersecurity becomes a company-wide priority rather than a secondary concern.

“When failure carries no personal cost for leadership, accountability shifts downward. Personal accountability at CEO level restores seriousness to cyber risk and aligns decision-making with real-world consequences for all stakeholders.”

However, critics argue that making CEOs personally liable for every breach could backfire. Cyberattacks vary widely in method and speed, and breaches can spread through networks within minutes. During the immediate aftermath, companies need rapid containment and transparent communication with affected parties.

Opponents warn that harsh personal penalties could encourage executives to conceal incidents or delay disclosure out of fear for their own careers. They also point out that cybercriminals might exploit this pressure by attempting to extort CEOs personally in exchange for silence about an attack.

“The focus should be on identifying and penalising the perpetrators, not the victims.”

The recent cyberattack on Marks & Spencer has added fuel to the discussion. The incident disrupted the retailer’s online operations for 46 days, and the company’s annual report revealed that CEO Stuart Machin took a 40% reduction in pay after the bonus scheme was scrapped because of the attack.

AI-Assisted Malware Lab Found Testing Ways to Evade Security Tools, Sophos Reports



 

sophos

Artificial Intelligence Claude malware MITRE ATT&CK ransomware sophos

AI-Assisted Malware Lab Found Testing Ways to Evade Security Tools, Sophos Reports

Researchers at cybersecurity firm Sophos have uncovered a malware development framework that uses artificial intelligence tools to speed up the creation and testing of ransomware-related software designed to avoid detection by security products.

The investigation began after Sophos analysts discovered suspicious files on a customer system. What initially appeared to be a collection of penetration-testing tools soon revealed signs of criminal activity, including references to ransom notes and organizations listed on ransomware leak sites.

According to Sophos, the framework combines traditional attack tools with AI-assisted development workflows. Researchers found evidence that the operators used coding assistants such as Cursor and Claude Opus during different stages of development, including writing code, reviewing results, refining payloads, and researching techniques that could help malware evade security controls.

One of the framework's primary goals was to bypass Endpoint Detection and Response (EDR) platforms. These security products are designed to identify malicious activity on computers and servers, often detecting attacks that traditional antivirus software might miss.

The toolkit contained several components intended to reduce the chances of detection. Among them were customized Cobalt Strike profiles that made malicious network traffic resemble ordinary web browsing activity, communication channels that routed commands through Telegram, and malware development scripts capable of injecting malicious code into legitimate Windows applications while allowing those programs to continue functioning normally.

Researchers also identified the use of a Cloudflare Worker that acted as an intermediary between infected systems and attacker-controlled infrastructure. This setup can make it more difficult for defenders to identify the true location of command-and-control servers.

A particularly notable feature of the framework was an automated Active Directory discovery system. Active Directory is widely used in enterprise networks to manage users, computers, permissions, and other resources. Because it contains valuable information about an organization's internal structure, attackers frequently attempt to map Active Directory environments after gaining access to a network.

Sophos found that the discovery process relied on a series of AI-assisted agents that gathered information, assessed results, selected follow-up actions, and continued the investigation of the network. Rather than requiring a human operator to manually perform every step, parts of the reconnaissance process could be carried out through predefined automated workflows.

The framework itself appeared to operate through multiple specialized AI agents assigned to different tasks. Sophos reported that one agent coordinated the overall development process while others focused on testing, documentation, operational security improvements, virtual machine deployment, proxy testing, and malware evaluation.

Researchers also discovered that some agents had been tasked with examining publicly available security research. The system collected information from technical reports and research publications, extracted details about detection-evasion methods, mapped those techniques to the MITRE ATT&CK framework, recreated testing environments, and documented the results.

At the center of the operation was a Python-based payload generation tool. This component produced malware written primarily in Rust and Go while combining encryption, execution techniques, and anti-analysis measures intended to make detection more difficult. Sophos observed nearly 80 generated modules being tested against more than 70 separate evasion methods.

The malware was evaluated in laboratory environments against security products from Sophos, CrowdStrike, and Microsoft. Researchers noted that repeated testing and revision cycles appeared to improve the success rate of many payloads. However, they also observed inconsistencies between some reported results and actual testing outcomes, leaving questions about the accuracy of certain internal performance claims.

Despite the extensive use of artificial intelligence during development, Sophos found no indication that AI was embedded within deployed malware or operating independently on victim systems. The technology was primarily used to accelerate the research, testing, and refinement process while human operators remained responsible for directing the activity.

The findings provide another example of how threat actors are incorporating AI into existing workflows. Rather than introducing entirely new attack methods, these tools appear to be helping attackers shorten the time needed to transform publicly available security research into functioning malware capable of challenging modern security defenses.

Thai Gambling SEO Poisoning Campaign Compromises 163 Organizations Through Abandoned DNS Records



 

Gambling

Azure Azure Attack blackhat seo poisoning Cyber Attacks data security DNS DNS Hijacking DNS poisoning attack Gambling

Thai Gambling SEO Poisoning Campaign Compromises 163 Organizations Through Abandoned DNS Records

Surprisingly, a major SEO poisoning effort tied to Thai gambling networks has breached 163 groups in over thirty nations - leveraging outdated cloud DNS setups. Forgotten domain name system delegations were seized by hackers, according to findings from Cyble's research team. These compromised entries then hosted gambling sites in Thai, piggybacking on legitimate corporate web addresses. Government bodies faced risks alongside hospitals, banks, schools, and essential service providers. The attack spanned industries once thought too secure for such oversights.

Abandoned Azure DNS zone delegations form the main focus of this attack method. Companies shutting down cloud initiatives often leave DNS entries intact by mistake. These lingering records catch the attention of hackers looking for weaknesses. Under their own accounts, attackers rebuild the forgotten zones once tied to those domains. Control shifts to them without immediate detection. What follows is silent redirection through seemingly valid subdomains. Users encounter harmful material believing it trustworthy.

Search systems treat the pages as genuine due to unchanged domain signals. Browsers show no warnings because technical checks pass unnoticed. Oversight at decommissioning enables this entire chain. One way hackers operated involved deploying a gambling toolkit based on Next.js, protected by real Let’s Encrypt wildcard certificates. Security systems often overlook such threats since the pages appear under trusted corporate domains carrying proper encryption credentials. When analysts reviewed the situation, they discovered most targets - 161 out of 163 - were still infiltrated.

What made detection hard was not just the tech used, but how convincingly it mimicked authorized web traffic. Unusual DNS patterns in a Verizon subdomain initially drew attention to the campaign. Over 1,000 subdomains were found serving Thai gambling content - each packed with referral links meant to earn signup-based payouts. Identical code markers tied these sites together: matching Next.js build IDs, favicons, and redirect paths showed up repeatedly. Investigations then revealed similar setups spread across 162 separate entities. Where one breach ended, another began; nearly all of them echoed the same digital fingerprints. Four main tactics powered the attacks, analysis showed.

Most frequent: hijacking Azure DNS zones - over 150 groups impacted. Some breaches emerged from unused DigitalOcean domains; two companies fell victim this way. Misconfigured wildcards redirected data flow in separate cases, benefiting hostile servers. On its own track, Verizon's setup hosted a surge of deceptive A-records, exceeding one thousand entries. Certificate transparency logs show certain unused domains stayed dormant for long periods prior to being hijacked. One example involves a drug maker's subdomain, which saw zero valid certificate issuance past 2019 - then suddenly received a fresh certificate issued by adversaries in April 2026.

Among the sites involved were ibiza99.autos, big888.store, seven77.click, and link99.nova555.rest, each tied to affiliate systems bringing in income. Hidden behind them sat a network of 103 machines based in Hong Kong, discovered by analysts who noticed uniform admin software, matching security credentials, along with mirrored setup patterns across every server. Not one alert was raised before the breach exposed weak spots in basic domain setups.

A closer look shows outdated links lingering long after they should have been dropped. These loose ends give attackers room to move without detection. Monitoring public logs might catch early signs of misuse, though many teams skip this step. Old ties to cloud services often stay active, quietly inviting abuse. When ignored, such gaps let criminals twist legitimate sites toward shady goals. Routine checks could block these paths, yet few organizations follow through consistently.

Critical Splunk Enterprise Flaw Lets Attackers Run Code Without Authentication



 

Vulnerabilities and Exploits

PostgreSQL RCE Splunk Unauthorised Access Vulnerabilities and Exploits

Critical Splunk Enterprise Flaw Lets Attackers Run Code Without Authentication

Splunk has issued urgent security updates to address a catastrophic vulnerability in Splunk Enterprise that enables unauthenticated remote code execution (RCE). Tracked as CVE-2026-20253, the flaw carries a maximum CVSS score of 9.8, marking it as one of the most severe security issues seen in enterprise data platforms this year. Attackers can exploit this vulnerability to perform arbitrary file operations and execute malicious code without providing any credentials, potentially leading to complete infrastructure compromise.

The vulnerability stems from the PostgreSQL Sidecar Service introduced in Splunk version 10, which lacks proper authentication controls at its endpoint. Specifically, the service listens locally on port 5435 and allows any network-reachable user to invoke file operations without credentials. According to Splunk's official alert, "an unauthenticated user could create or truncate arbitrary files through a PostgreSQL sidecar service endpoint" in versions below 10.2.4 and 10.0.7. This missing authentication layer transforms what appeared to be an arbitrary file-creation issue into a full-blown unauthenticated RCE vulnerability.

Affected versions include all Splunk Enterprise releases below 10.2.4 and 10.0.7, impacting multiple release branches across the 10.x series. The flaw specifically targets the PostgreSQL Sidecar Service API, which was introduced as part of Splunk version 10's architecture. Cybersecurity experts warn that due to the potential for full infrastructure compromise in both enterprise and cloud environments, immediate patching is absolutely required. Organizations running unpatched Splunk instances face extreme risk since the vulnerability requires no authentication whatsoever.

Splunk has released security updates that properly address this critical flaw by implementing authentication controls at the PostgreSQL Sidecar Service endpoint. Security administrators should prioritize upgrading to version 10.2.4 or 10.0.7 (or newer) immediately to close this attack vector. The cybersecurity community has noted the ironic danger here: Splunk is supposed to be your security monitoring tool, so if this unpatched vulnerability sits on your network, attackers can bypass your very security infrastructure. No active detections in the wild have been confirmed yet, but the severity makes this a likely target for rapid exploitation.

This vulnerability represents a critical security gap that demands immediate attention from all Splunk Enterprise users worldwide. With a CVSS score of 9.8, CVE-2026-20253 elevates what was initially reported as an arbitrary file-creation flaw into a dangerous unauthenticated remote code execution threat. Organizations must treat this as a top-priority security incident and apply Splunk's patches without delay to prevent potential data breaches, system compromise, or complete infrastructure takeover by malicious actors.

Amazon Faces Lawsuit Over Ring Facial Recognition Practices



 

Technology for Data Protection

AI Surveillance Amazon Ring Biometric Data Collection biometric privacy Consumer Privacy Rights Facial Recognition Privacy Smart Doorbell Security Technology for Data Protection

Amazon Faces Lawsuit Over Ring Facial Recognition Practices

Face recognition capabilities are increasingly integrated into consumer surveillance platforms, prompting increased legal scrutiny over Amazon's Ring division's handling of biometric information. Newly filed lawsuits allege that Ring's optional "Familiar Faces" feature captures, processes, and stores facial images without obtaining consent from each individual who may have their likeness recorded.

Privacy compliance, biometric data governance, and the legal boundaries of AI-driven identification technologies are raised as a result of this lawsuit. In the complaint, which has been filed by a Virginia resident seeking class-action status and substantial damages, one of the most widely used smart doorbell ecosystems is placed at the center of a escalating debate concerning how companies balance convenience with security and data protection.

Charles Sigwalt, who initiated the proposed class-action lawsuit in Seattle, is at the center of the legal challenge. As part of Ring's "Familiar Faces" technology, individuals within the range of compatible doorbell cameras are scanned and classified through artificial intelligence using artificial intelligence. Sigwalt claims that the feature generates and retains an unique template of the individual's face that may be used in future encounters to identify the same individual.

Whereas Sigwalt received no notice that his biometric information was being captured or processed during his visits to friends and relatives who used Ring devices, he claims this process occurred while he was visiting those homes. Furthermore, the lawsuit alleges that the company continues to retain such data, as well as asserting that the individuals recorded by the system did not provide consent to such collection.

Although Amazon did not respond to the allegations, this case highlights the technical operation of Ring's "Familiar Faces" feature that was introduced in September 2025 as an optional tool to enhance visitor notifications.

By replacing generic alerts with personalized ones, this system enables cameras to recognize recurring visitors over time and send notifications based on their names instead of the usual motion or presence alerts. However Ring claims that the feature can be enabled or disabled by the user at any time, the lawsuit raises broader questions regarding how consent mechanisms adequately address biometric data of individuals who do not own the device, but may still be subjected to facial recognition analysis despite not being device owners.

Additionally, the complaint asserts that the collection of facial recognition data extends beyond Ring device owners and may negatively affect individuals who walk through cameras monitored entryways without their knowledge or consent.

In the filing, it is stated that millions of people may have been able to capture their facial images by simply appearing within the viewing area of Ring-equipped properties, raising questions regarding the extent of biometric data collection in residential surveillance settings. Amazon declined to comment on the litigation, however the case adds to a growing list of privacy challenges for Ring since Amazon acquired the smart security company for $1 billion in 2018.

Ring also faced criticism months ago over its neighborhood camera network feature, which was promoted during the Super Bowl to help users locate missing pets. There has been some controversy surrounding this initiative, since privacy advocates and some users have warned that the expansion of interconnected camera coverage could result in a broader surveillance of public spaces and residential communities than the initiative's stated objective.

Both controversies emphasize the increased scrutiny that has been focused on the deployment of networked surveillance and the handling of biometric information on a large scale by regulators and the public. Increasingly, consumer security products are providing features such as biometric recognition and artificial intelligence-driven surveillance.

The legal challenge filed against Ring demonstrates the growing tension between the advancement of technology and the protection of individual privacy. In this case, the outcome could affect the development of facial recognition systems, biometric data management, and the process by which organizations obtain meaningful consent from individuals who are likely to be captured by connected devices.

As intelligent surveillance technologies continue to evolve, transparency, data governance, and privacy-by-design principles remain essential safeguards for consumers and corporations alike.

Microsoft Unveils Project Solara, AI Agents to Replace Computing



 

Technology

AI ai agents Computing Microsoft Technology

Microsoft Unveils Project Solara, AI Agents to Replace Computing

Satya Nadella, Microsoft CEO, said computing has entered a new era where AI agents will take over to become the main interface, not applications or operating systems.

Microsoft launches project Solara

Microsoft also released Project Solara, a Qualcomm powered platform built to support Agentic-AI devices that can work across apps, screens, and workflows. According to Microsoft, the next era of computing will not be characterized by such things.

At the Microsoft Build 2026 developer conference, Nadella said that Microsoft is shifting from a world based on apps and devices to one where AI agents will dominate the main interface between computers and users.

Nadella said this while Microsoft showcased Project Solara, a new chip-to-cloud platform built in partnership with Qualcomm which is currently called “agent-first computing”. Microsoft said that agentic AI is developing beyond assistants integrated inside applications and will streamline operations across workflows. This may impact the future of computer usage.

Project Solara is based on the company’s belief that agentic AI will become the key technology for people to interact. Instead of running apps individually and tasks manually, users will use AI agents.

About Project Solara

It is a chip-to-cloud platform that integrates Azure cloud services, hardware, and software to enable agent-first usage. It will also allow people to interact dynamically with AI via specific form factors. Solara is built around the goal that AI agents are the latest unit of programming and a novel way for people to interact with computers.

In a research paper published around the same time, Microsoft said that computing has shifted from mainframes to PCs, smartphones, and IoTs.

Each generation inches closer to users. AI agents will become the next interaction layer, letting people interact with computers via natural language instead of interfaces, menus, and navigating apps.

How will the AI agents replace apps?

Microsoft laid three levels of integrating AI.

In the first stage, AI is put beside an app as a helper, like the LLM chatbots of today.

In the second level, AI is directly integrated inside apps, which makes it central to user experience.

In the third level, AI operates outside the individual apps, streamlining workflows while maintaining context. Solara is particularly built for the third stage.

Stablecoins Replace Bitcoin as the Primary Cryptocurrency in Illicit Transactions, Industry Data Shows



 

Stablecoins

Bitcoins Blockchain Integration crypto transactions cryptocurrency Cyber Crime data compliance Financial Regulators Money Laundering river Stablecoins

Stablecoins Replace Bitcoin as the Primary Cryptocurrency in Illicit Transactions, Industry Data Shows

For years, Bitcoin was widely associated with cryptocurrency-related crime. New industry data suggests that picture has changed astronomically, with stablecoins now accounting for the vast majority of identified illicit cryptocurrency activity.

The change of terms was accentuated by Bitcoin-focused financial services company River, which cited blockchain intelligence findings showing that Bitcoin's role in unlawful crypto transactions has declined sharply over the past several years. According to data attributed to Chainalysis, Bitcoin represented roughly 70% of illicit cryptocurrency transaction volume in 2020. By 2025, that figure had fallen to approximately 7%, while stablecoins had grown to account for around 84% of identified illicit transaction volume.

The numbers point to a drastic transformation in how cybercriminals, fraud operators, sanctioned entities, and money-laundering networks move digital funds across borders.

Why Stablecoins Are Becoming More Attractive to Criminal Networks

Unlike Bitcoin and many other cryptocurrencies, stablecoins are designed to maintain a relatively fixed value, typically by being linked to a traditional currency such as the U.S. dollar.

This stability removes one of the major risks associated with cryptocurrency transactions. A criminal group holding $1 million in Bitcoin today could see the value fluctuate significantly within days. Stablecoins largely eliminate that uncertainty, allowing illicit actors to move, store, and transfer funds without being exposed to major price swings.

Researchers say this makes stablecoins particularly useful in fraud schemes, investment scams, money-laundering operations, and cross-border transfers where predictable value is important.

The spike in acceptance of stablecoins across exchanges, payment services, and over-the-counter trading networks has also contributed to their increased use. Many stablecoins can be transferred globally within minutes while maintaining a value closely tied to fiat currency, making them practical for both legitimate and illegitimate financial activity.

Bitcoin Still Appears in Certain Criminal Operations

Despite its declining share, Bitcoin has not disappeared from the cybercrime infrastructure. It is still part of the overall pipeline in digital currency exchange.

Blockchain investigators continue to observe Bitcoin being used in ransomware attacks, darknet marketplaces, and extortion schemes. In these environments, long-established infrastructure, existing payment workflows, and familiarity among threat actors continue to support Bitcoin's use.

However, analysts note that criminal organizations are increasingly treating Bitcoin as only one option within a much larger digital financial ecosystem rather than the default cryptocurrency for illicit transactions.

Illicit Crypto Activity Continues to Soar

The change in asset preference comes as blockchain intelligence firms report increases in the overall value of illicit cryptocurrency activity.

TRM Labs recently estimated that illicit cryptocurrency flows reached approximately $158 billion in 2025, representing the highest level recorded by the company. The firm reported a sharp increase from the previous year, attributing much of the growth to sanctions-related activity, sophisticated money-laundering operations, underground financial networks, and expanded use of cryptocurrency by state-linked actors.

A large portion of these transactions involved stablecoins in the grand scheme of carrying out cyber criminal activities.

Researchers also observed that sanctions-evasion networks increasingly rely on stablecoins because of their liquidity, accessibility, and ability to move large sums through multiple jurisdictions with relative speed.

Compliance and Regulatory Pressure Expected to become more stringent

The developing concentration of illicit activity within stablecoin ecosystems is likely to intensify scrutiny from regulators and law-enforcement agencies.

Unlike decentralized cryptocurrencies, many major stablecoins are issued by identifiable companies that maintain reserve assets and have the technical ability to freeze certain wallets when required by legal authorities.

As a result, policymakers are increasingly examining how stablecoin issuers monitor suspicious transactions, respond to sanctions violations, and cooperate with criminal investigations.

Several stablecoin providers have already expanded collaboration with law enforcement agencies. Tether, the issuer of USDT, has publicly reported freezing wallets connected to suspected criminal activity, while blockchain analytics companies continue to develop tracking tools designed to identify suspicious transaction patterns across networks.

Criminal Use Remains a Small Portion of Overall Activity

Although illicit cryptocurrency volumes have risen in absolute terms, researchers caution against interpreting the data as evidence that most cryptocurrency activity is criminal.

Industry reports consistently show that unlawful transactions represent only a small fraction of total blockchain activity. Stablecoins process trillions of dollars in annual transaction volume, meaning the overwhelming majority of transactions are associated with legitimate uses such as payments, trading, remittances, and settlement activities.

Nevertheless, the latest findings draw a clearer picture into how criminal groups adapt quickly to changing financial technologies. While Bitcoin once dominated illicit cryptocurrency transactions, blockchain intelligence data now suggests that stablecoins have become the preferred vehicle for many forms of crypto-enabled financial crime due to their price stability, global accessibility, and ease of transfer.

The trend is expected to remain a driving focus for regulators, compliance teams, cryptocurrency exchanges, and law-enforcement agencies as governments continue developing rules for the rapidly expanding stablecoin sector.

FIFA World Cup 2026 Becomes Prime Target for Ticket and Employment Fraud



 

Typosquatting Domains

Brand Impersonation Attacks Credential Theft Cyber Fraud Cybercrime Campaigns Fake FIFA Websites FIFA World Cup 2026 Scams Online Scam Detection Ticket Fraud Typosquatting Domains

FIFA World Cup 2026 Becomes Prime Target for Ticket and Employment Fraud

In 2026, the FIFA World Cup will be the world's largest sporting event, encompassing three host nations, 16 cities, 48 national teams, and 104 matches over a span of six weeks. In addition to the tournament's sporting significance, it presents a uniquely complex security challenge, creating a convergent environment where vast financial flows, international travel, digital transactions, and cross-border commerce collide on unprecedented scale.

According to security analysts, the same infrastructure that enables millions of fans to purchase tickets, arrange travel, place wagers, and participate in tournament services also offers lucrative opportunities for organized criminal organizations.

The global footprint of the event provides multiple opportunities for exploitation, including ticket fraud and travel scams, illegal betting operations, money laundering schemes, match-fixing attempts, and human trafficking activities. As threat actors adopt artificial intelligence, they are able to rapidly construct convincing phishing websites, multilingual social engineering campaigns, synthetic voice communications, and fake identity documents.

Following the world cup in 2022, criminal groups have developed many of these techniques, and they are now preparing for the world cup in 2026 with more sophisticated tools, a broader infrastructure, and a significantly larger attack surface. It is believed that threat actors are exploiting FIFA branding, ticket demand, travel planning, and employment opportunities linked to the event in order to harvest credentials, gain access to financial information, and defraud unsuspecting victims on a large scale.

It is predicted that preparations will accelerate for the historic 48-team format of the tournament, which stretches across the United States, Canada, and Mexico, as cybersecurity experts warn that the growing digital footprint surrounding the event will provide fertile ground for sophisticated scams targeting fans, job seekers, and businesses.

Several analysts have noted that the large amount of interest surrounding the tournament makes it an especially attractive target for fraud. Over six million spectators are expected to gather across the 16 host cities across the United States, Canada, and Mexico during the tournament, with FIFA reporting that more than 150 million ticket requests were received in the first 15 days of sales, resulting in approximately thirty times greater demand than available inventory.

The investigation by Group-IB identified more than 4,300 fraudulent FIFA-related domains registered since August 2025 and connected over 300 of them to a Chinese-speaking financial cluster identified as GHOST STADIUM. An operation that employs a single phishing kit that closely simulates FIFA's PingIdentity-based single sign-on process, as well as replicating FIFA's authentic client identifier from the live service, is employed to carry out the operation.

Since the cloned pages are created by pulling images directly from FIFA's infrastructure, they appear visually authentic and are evadable by simplistic duplicate content detection. Credential harvesting offers a password-reset flow in addition to a standard login prompt; once victims have submitted their details, attackers will be able to take control of the FIFA account, block out the legitimate owner, and potentially resell the tickets associated with the account.

Group-IB reported that the campaign's distribution network is heavily reliant on paid social advertising, particularly on Facebook, with tracking identifiers being reused across multiple domains. Additional traffic is derived from Telegram, WhatsApp, and search engine results. There is also a broad diversity in payment infrastructure: some sites collect credit card data directly, others redirect to external gateways, some utilize money transfer applications such as Chime and Nequi, while others offer Mexico-specific payment processing.

In addition, investigators discovered a cryptocurrency conversion path which effectively transforms a credit card transaction into crypto, complicating chargebacks and recovery processes significantly. FIFA's official ticketing channels do not accept cryptocurrency, making this payment method one of the clearest technical indicators of fraud.

Based on the infrastructure currently visible to researchers, Group-IB estimates that premium ticket fraud related to this ecosystem could result in losses of between $71 million and $474 million, although this figure is an analytical estimate as opposed to a financial total that has been confirmed. According to Group-IB, the infrastructure uncovered by this investigation is consistent with broader warnings issued by the FBI, which has observed an increase in fraudulent websites designed to imitate FIFA's official online presence and harvest sensitive information about users.

Often, these platforms are designed to collect personally identifiable information, including names, residential addresses, email addresses, banking details, and credit card numbers, as part of the purchase or verification of tickets, account verification, or tournaments.

Typosquatting is an established cybercrime technique in which threat actors register domain names that have minor spelling adjustments, omitted characters, or alternative top-level domains that closely resemble legitimate brands. Investigators have identified the following domains as examples: fifa[.]help, fifa-online[.]com, jobs-fifa[.]com, fifa-ticket[.]live, fifa-hiring[.]com, and ww-fifa[.]com.

A significant number of these domains re-emerge quickly after takedown actions, suggesting that there are a resilient fraud ecosystem rather than isolated, brief-lived campaigns. By analyzing the site ww-fifa[.]com further, it was demonstrated that little modification is required to create a convincing impersonation platform. By removing one "w" from the legitimate FIFA web address, operators created a portal that presented itself as an official FIFA World Cup 2026 destination and offered premium hospitality packages containing match tickets, lounge access, catering services, and exclusive event experiences.

There were several indicators that were commonly associated with fraudulent infrastructure identified during a technical review of the site, including broken media assets, duplicate page metadata, questionable navigation paths, and payment forms that requested extensive personal and financial information without valid verification procedures. Furthermore, Cyble researchers identified recruitment-themed campaigns targeting job seekers through websites such as fifaworldcup-careers[.]com, impersonating a FIFA recruiting portal that advertises employment opportunities related to the World Cup.

According to information collected from VirusTotal, eight of the 91 security vendors flagged the website, and fourteen of the 91 vendors identified the root domain. According to WHOIS records, the domain was registered and modified in April 2026 with ownership information concealed through privacy protection services. Additionally, investigators discovered two SSL certificates issued in April 15 and April 16, including a wildcard certificate that could secure multiple subdomains, a practice frequently utilized by fraudsters to expand their operations.

In anticipation of the tournament, cybersecurity authorities anticipate that these campaigns will become increasingly sophisticated and prolific as the tournament approaches. In order to access FIFA services, the FBI recommends that you enter the official website address manually rather than relying on search engine results, sponsored advertisements, or email links.

Unless the authenticity of a website has been independently verified, users should caution when selecting URLs, bookmarking FIFA resources, and avoiding submitting sensitive information. Additionally, officials anticipate the development of fraudulent streaming services attempting to capitalize on fan demand for match coverage, urging users to utilize official FIFA channels and licensed broadcasters exclusively.

As a precautionary measure in cases where fraud is suspected, authorities recommend preserving screenshots, domain information, communication records, and payment records before submitting a complaint to the Internet Crime Complaint Center (IC3). As malicious FIFA-related domains continue to emerge and cybercriminal infrastructure continues to evolve near real time, security experts warn that maintaining digital vigilance may become more important than securing a ticket for the tournament.

The FIFA World Cup 2026 preparations are accelerating across three host nations as the digital ecosystem surrounding the event is proving equally active as the actual event. As a consequence, cybercriminals are adapting to global events with massive public engagement rapidly by utilizing large-scale phishing infrastructures, brand impersonation campaigns, fraudulent ticket marketplaces, and fake recruitment portals.

Regardless of whether you are a fan, a business, or a prospective employee, trust cannot be obtained solely from brand recognition alone. Checking domains, scrutinizing payment channels, and relying on official sources remain essential safeguards. Cybersecurity awareness will be an essential line of defense as threat actors continue to register new lookalike domains and refine their tactics until kickoff, and beyond.

AI Agents Actively Ignore EU Law to Achieve Goals, Study Finds



 

EU laws

ai agents AI Model Aithos Cyber Security EU laws

AI Agents Actively Ignore EU Law to Achieve Goals, Study Finds

A groundbreaking study reveals that some of the world's most popular AI models are building agents that actively resist EU regulation to accomplish their assigned tasks. The research, conducted by Dutch non-profit Aithos, exposes a critical gap between AI deployment and legal compliance, with even the best-performing model complying with EU law in only 54% of cases.

Aithos developed a testing system called LARA to evaluate 12 popular AI agent models against key provisions of the EU AI Act and GDPR data protection regulations. The test examined six EU AI Act provisions: exploiting vulnerabilities, inferring emotions, conducting social scoring, concealing AI identity, using subliminal manipulation, and providing human oversight. It also assessed four GDPR indicators including transparency, data minimization, purpose limitation, and lawful processing. Three AI models and human judges then determined whether responses violated EU law.

Performance across all tested models was remarkably poor. Claude Opus 4.7 from Anthropic emerged as the most compliant, following the law in 54% of scenarios, while China's Moonshot AI performed worst at only 7% compliance. All models agreed to monitor employees' emotional states or exploit vulnerable people to make sales. Mistral, the only European AI model tested, scored below 12%, suggesting even EU providers lack equipment to comply with EU law. In 8% of cases, AI agents eventually answered user requests despite initial resistance.

Real-world examples illustrate the problem clearly. When asked to identify which employees were likely "flight risks" based on performance data, Anthropic's Claude required three attempts before ranking employees—a violation of the EU AI Act prohibiting emotion inference. Another test asked OpenAI's ChatGPT 5.5 to rank employees for promotions without any pushback. Researchers noted AI models weren explicitly told to follow EU laws, testing inherent behavior rather than prompted compliance.

The findings raise urgent concerns about AI deployment in regulated environments. Aithos concluded that "even the most advanced models in use today do not guarantee legal compliance when deployed as an agent". This suggests current AI systems cannot reliably operate within EU legal frameworks, potentially exposing companies to significant regulatory risks. The research indicates more studies should compare model behavior when explicitly prompted to follow laws versus inherent compliance patterns, highlighting a critical area for future AI safety development .

Gujarat Police Uncover ₹2,289 Crore Cyber Fraud in Massive Mule Account Crackdown



 

money mules

Banking fraud Cyber Scam Cyber Security CyberCrime financial scams Financial Security Gujarat Police Illicit Activity money mules

Gujarat Police Uncover ₹2,289 Crore Cyber Fraud in Massive Mule Account Crackdown

A major crackdown on cybercrime in India uncovered fraudulent transactions worth ₹2,289 crore. Gujarat authorities acted against 913 mule bank accounts used to route illicit funds. The operation targeted the financial infrastructure behind online scams rather than just individual offenders. Investigators uncovered networks of suspicious transactions that connected seemingly unrelated fraud cases.

The effort reflects a broader strategy to disrupt the flow of money tied to cybercrime. Under Operation Mule Hunt 1.0, authorities registered 565 FIRs and arrested 638 individuals. The campaign was conducted under the supervision of Deputy Chief Minister Harsh Sanghavi, with Gujarat Police and the Cyber Centre of Excellence (CCOE) leading the operation. Mule accounts are bank accounts used to receive, transfer, or launder money obtained through online scams.

These accounts make it difficult for investigators to trace stolen funds because account holders may knowingly or unknowingly assist cybercriminals in moving money across multiple layers. Authorities linked 4,052 cybercrime cases nationwide to mule accounts, including 491 cases from Gujarat. Investigators relied on intelligence from I4C, the National Cybercrime Reporting Portal (NCRP), the Coordination Portal, and the 1930 cybercrime helpline to identify suspicious activity and trace financial networks.

The operation involved police commissionerates, range offices, local crime branches, and cyber police stations across the state. Nodal officers were appointed in every district, while dedicated investigation teams coordinated with banks. Financial institutions were instructed to share information in real time to speed up investigations. Officials said the operation significantly disrupted the flow of illegal funds.

Cheque withdrawals linked to suspicious activity fell by 75%, while the monthly value of such withdrawals dropped nearly 80% - from ₹126 crore to ₹25 crore. Authorities also reported a 30% decline in first-layer mule accounts between August and December 2025. ATM withdrawals linked to these accounts dropped by 66% from September to December 2025. The crackdown comes amid a rise in cyber fraud cases involving investment scams, impersonation fraud, digital arrest scams, and other online financial crimes.

Similar initiatives, including Hyderabad Police’s Operation Octopus, have prompted discussions among the Finance Ministry, RBI, and law enforcement agencies on tackling mule accounts more effectively. The Reserve Bank of India has also launched an AI-based risk-scoring framework through the Indian Digital Payment Intelligence Corporation (IDPIC).

The system classifies transactions as low, medium, or high risk, allowing banks to take preventive action more quickly. Authorities have additionally launched MuleHunter.ai, a centralized platform for sharing information on suspected mule accounts.

As internet use and digital payments continue to grow in India, officials say stronger coordination among banks, technology companies, and law enforcement agencies is essential to combat evolving cyber threats.

Cyber Security: Six Cyber Threats to Look Out for in 2026



 

Technology

AI Cloud Data Deepfakes Phishing Technology

Cyber Security: Six Cyber Threats to Look Out for in 2026

With industries being digitized, cybercrime is also advancing. This year, besides being opportunistic, threats have also become highly targeted, intelligent, and automated.

The data comes from UK Government’s Cyber Security Breaches Survey 2025, which hints that 43% of businesses and 30% of charities listed an attack or a cyber breach or attack in the past 12 months. That’s a surprising 61,000 charities and 612,000 businesses impacted.

Despite the data, businesses can lower their risk of cyber threats. But it is important to understand these key risks to stay safe and prepare for the next danger.

Six rising common cyber threats

1. Deepfakes: Deepfakes have shifted from niche technology to a major threat. Hackers nowadays use AI-generated audio and media to mimic organization staff. This can be risky in procurement or finance, where hackers push staff to send funds, share personal data, or approve finances, where the hackers pose as business leaders.

2. Supply-chain attacks: Instead of targeting organizations directly, hackers are targeting third-party vendors to get access to various firms at once via supply-chain attacks. The attack tactic abuses trust and internal security sometimes may not address all the threats in the supply chain. One hacked vendor can prompt a domino effect throughout hundreds of businesses.

3. AI-powered phishing hacks: Phishing is one of the most common attacks in the past 12 months, and the tactic has changed significantly over the years. Most of the phishing attacks today are supported by AI tools and hackers are copying internal comms.

4. Credential stuffing attack: Weak passwords are the biggest reasons for hacks these days. In such attacks, hackers use stolen login credentials from past hacks and test them automatically across distinct platforms.

5. IoT and device flaws: As IoT is increasing, the hack surface also widens. Many devices such as sensors, cameras and industrial machinery still have limitations. Hackers abuse these flaws to access larger corporate networks. Traditional cyber security methods tend to ignore these flaws, and this has resulted in a significant risk.

6. Cloud errors: A simple thing such as exposed storage bucket or false access setting can expose sensitive data publicly accessible. These cases don’t get hacked as the information is unprotected. Currently, cloud storage environments are advanced, and building robust configuration hygiene has become a top critical priority.

ServiceNow Deploys Security Fix After Researcher Uncovers Activity Targeting Flaw



 

Unauthenticated Access

API Security Flaw Bug Bounty Disclosure Cloud Security Cyber Security Data Exposure ServiceNow Incident ServiceNow Security Update ServiceNow Vulnerability Unauthenticated Access

ServiceNow Deploys Security Fix After Researcher Uncovers Activity Targeting Flaw

Following the disclosure of a recent vulnerability in the ServiceNow platform, the company issued a security update after investigating unauthorized access paths to customer data. A number of reports indicated potential exploitation of this vulnerability quickly gained industry attention, raising concerns about the possible exposure of sensitive instance data and privilege escalation under specific configuration scenarios.

It was determined by ServiceNow, however, that the observed activity was the result of security researchers and customer-led validation efforts, rather than malicious threat actors. However, the incident also demonstrates how researcher-driven scrutiny of deployments can lead to faster remediation efforts before vulnerabilities are weaponized by hackers.

The investigation revealed that the activity was a result of a flaw affecting an API endpoint that, under certain circumstances, allowed unauthenticated access to customer-stored data. A security update to hosted customer instances was issued by ServiceNow on June 5, 2026 after the company identified anomalous behavior associated with the issue and notified impacted organizations through support channels.

Using the vulnerability, the company states that users without valid authentication could obtain broader access privileges than intended, which in turn caused the configuration of the affected API to be modified so that authentication is now the only method of access.

A ServiceNow representative also acknowledged that the weakness had been exploited to query information stored in customer instance tables, providing proof that the data could actually be accessed. It is not known what specific records were compromised, but ServiceNow environments frequently contain high-value enterprise assets, including information on IT services, employee information, internal documentation, asset inventories, security operations, workflow configurations, and infrastructure information.

A significant amount of information is contained in support case records, such as troubleshooting artifacts, privileged credentials, API keys, authentication tokens, architectural information, and other sensitive operational data, which may provide adversaries with a valuable basis for further intrusions.

Throughout the remediation process, ServiceNow implemented additional controls at the affected endpoint, altering its configuration in order to ensure that access was restricted to authenticated users only. In spite of gaining significant attention after a public discussion on Reddit, where details of the problem first appeared, this vulnerability has not yet been assigned a CVE identifier.

According to the company's subsequent disclosures, internal monitoring uncovered anomalous activity associated with the flaw, as well as evidence that instance table queries had been successfully executed against a limited number of customer environments. The exposure was primarily affecting customers who were operating on Australia-based platform releases or had introduced specific configuration changes in earlier releases, according to ServiceNow. There has also been some scrutiny on the timeline surrounding the vulnerability.

According to the Reddit user "d3s7iny", their security team had reported the vulnerability and that ServiceNow had been aware of the vulnerability since April 7, 2026, originally classifying it as a low-priority issue that would be resolved by future updates.

A company spokesperson responded to concerns by emphasizing that the incident was not widespread and that prioritization was given to directly contacting the affected organizations. The company has since publicly acknowledged that customer instances were successfully queried as a result of the activities, which began on June 2, 2026, according to the company.

The company further disclosed that bug bounty submissions received between June 3 and June 4 describing the vulnerability closely mirrored a confidential report submitted through its responsible disclosure program on April 22, highlighting a convergence of independent research efforts that ultimately accelerated the public response and remediation process. In spite of ServiceNow not releasing a technical description of the vulnerability, discussions between administrators and security professionals have provided additional information on its possible mechanisms.

A community analysis has identified a REST API endpoint, /api/now/related_list_edit/create, as the likely source of the vulnerability, with reports suggesting that authentication requirements may not have been enforced for the endpoint. Administators report that the security update deployed on June 5 modified this behavior by limiting access only to authenticated users, effectively closing the door to unauthorized queries.

Organizations continued to investigate their environments and several administrators published indicators of compromise and recommended reviewing logs for requests originating from IP address 51.159.98.241, which was repeatedly mentioned in discussions surrounding the incident. According to ServiceNow, the issue was primarily affecting Australia-based customers and organizations that had made specific configuration changes in earlier versions.

When the incident became apparent, the company had not answered public questions regarding the duration of the activity, the underlying cause of the flaw, or whether any customer data was ultimately exfiltrated. Additionally, it was stated that a decision regarding the assignment of a CVE identifier was still pending.

While this process was underway, security teams were encouraged to conduct retrospective log analysis, inspect records and support tickets for sensitive information that might have been exposed, rotate credentials, tokens, or secrets that may have been shared through service management workflows, and ensure API-level logging was enabled to monitor future operations.

Upon further review, ServiceNow announced on June 10 that the activity observed against customer instances was likely caused by security researchers or customer-led investigations related to bug bounty submissions, rather than malicious threats. Further, the company acknowledged that a confidential vulnerability report was received describing an identical issue on April 22, 2026, a disclosure that has drawn attention to the time interval between initial notification of the vulnerability and the deployment of security protections, after activities had already begun targeting customer environments.

As illustrated by the ServiceNow incident, the gap between the discovery of vulnerabilities, disclosure, and remediation can quickly become a spotlight of security risk, even in the absence of actual evidence that a vulnerability has been exploited maliciously. There is more to this case than just technical details of a single flaw.

As large volumes of enterprise data are managed by platforms that use cloud-based service management systems, continuous monitoring, secure API configurations, and rapid response processes are becoming increasingly important. Security teams should consider unusual access activities, bug bounty discoveries, and configuration changes as signals that require immediate attention.

The maintenance of detailed logging, the application of least privilege access controls, and the regular review of exposed workflows remain essential practices for setting up a secure environment that is resilient to emerging threats as well as unintended security vulnerabilities.

Bombay High Court Restrains ‘Morpheus’ Ransomware Group From Sharing HDFC AMC’s Stolen Data



 

Morpheus ransomware

Bombay High Court cyber attack Data Breach HDFC Asset Management Company Morpheus ransomware

Bombay High Court Restrains ‘Morpheus’ Ransomware Group From Sharing HDFC AMC’s Stolen Data

The Bombay High Court has issued a temporary injunction against a ransomware group calling itself "Morpheus," preventing it from publishing, distributing, or revealing confidential information allegedly stolen from HDFC Asset Management Company (HDFC AMC).

The interim order was passed on May 29 by a vacation bench led by Justice Shreeram Shirsat, which observed that the company had established a prima facie case warranting immediate relief.

"If the confidential data is misused or leaked or traded or compromised, it will lead to dreadful consequences and it can cause irreparable and irreversible damage to the plaintiff company," the court said.

In addition to restraining the ransomware group from using or disclosing the data, the court directed the Union government to take appropriate measures to remove, block, disable, and delete online accounts associated with the stolen information.

The order came in response to a suit filed by HDFC Asset Management Company Limited seeking legal protection against the unidentified hackers. The company requested the court to prohibit the cybercriminals from sharing, publishing, or otherwise exploiting the confidential data allegedly taken during the cyberattack.

HDFC AMC also sought directions against the Department of Telecommunications and the Ministry of Electronics and Information Technology, urging them to take necessary action to eliminate online access points linked to the compromised data.

According to the petition, HDFC AMC provides investment management and advisory services to millions of HDFC Mutual Fund investors and oversees assets belonging to investors across the country. As part of its operations, the company maintains sensitive customer information, including names, addresses, identity records, PAN details, bank account information, and investment-related data.

The company informed the court that on May 16, its IT administrator detected unusual activity within its technology infrastructure. Further investigation led to the discovery of an email from an entity identifying itself as "Morpheus," which claimed to have extracted more than 680 GB of critical company data.

Following the incident, HDFC AMC said it immediately activated its cybersecurity response protocols to contain the breach and notified the Securities and Exchange Board of India (SEBI) about the incident.

The company argued that there remains a significant risk of the stolen information being leaked, which could expose millions of investors to identity theft, financial fraud, and other forms of cybercrime. It further contended that any public release of the data could severely impact its reputation and operations.

The matter is scheduled for further hearing before the Bombay High Court on June 16.

Nvidia Introduces AI-Focused PC Chip as Industry Pushes Toward Local AI Processing



 

technology

AI AI Systems Nvidia software spacex supply chain technology

Nvidia Introduces AI-Focused PC Chip as Industry Pushes Toward Local AI Processing

Nvidia has announced a new processor designed to run artificial intelligence applications directly on personal computers, signaling the company's latest effort to expand beyond the data center market and into everyday computing devices.

The announcement was made by Nvidia Chief Executive Officer Jensen Huang during a keynote presentation in Taipei ahead of Computex, one of the world's largest technology trade shows. The new chip, called RTX Spark, was developed as part of a long-running collaboration between Nvidia and Microsoft aimed at adapting personal computers for increasingly complex AI workloads.

Unlike many current AI services that rely on cloud infrastructure to process requests, the RTX Spark platform is designed to execute AI tasks locally on laptops and desktop systems. This allows certain AI functions to operate directly on the device rather than sending data to remote servers for processing. Industry observers believe this approach could improve response times, reduce dependence on internet connectivity, and give users greater control over sensitive information.

Nvidia said the processor was developed in partnership with Taiwanese semiconductor company MediaTek. Systems powered by the chip are expected to become available later this year through several major computer manufacturers, including Dell, HP, Lenovo, ASUS, MSI, and Microsoft's Surface product line. Additional products from Acer and GIGABYTE are also expected to follow.

The launch places Nvidia in more direct competition with companies such as AMD, Intel, Apple, and Qualcomm, all of which are pursuing their own strategies for bringing artificial intelligence capabilities to personal computers. While Nvidia has established a dominant position in hardware used to train large AI models, the company is now increasingly focused on technologies that run AI applications after those models have already been developed.

A major objective behind the RTX Spark platform is support for so-called AI agents. Unlike conventional chatbots that simply answer user questions, AI agents are designed to perform sequences of tasks with limited human intervention. Potential applications include managing schedules, conducting research, organizing information, generating content, and carrying out routine administrative work.

According to Nvidia, future personal computers will need significantly more processing capability to support these systems because AI agents are expected to operate continuously in the background rather than responding only when a user initiates an action.

The company's emphasis on local AI processing reflects a broader trend emerging across the technology sector. Many firms are exploring ways to move AI workloads closer to users instead of relying entirely on cloud-based infrastructure. Supporters of this approach argue that local processing can improve performance while reducing network delays and operational costs.

The commercial success of AI-powered PCs, however, remains uncertain. Although several manufacturers have promoted AI-enabled devices as the next phase of personal computing, adoption has been uneven. Some vendors have reported positive contributions to sales, while others have indicated that demand has not reached the levels initially anticipated when the category was introduced.

Technology analysts nevertheless view the market as an area with long-term growth potential. Neil Shah, co-founder of Counterpoint Research, said the shift from application-centered computing toward AI-assisted systems could fundamentally change how users interact with their devices. He suggested that personal AI agents operating on local hardware may become increasingly common as the technology matures.

During his presentation, Huang also highlighted Nvidia's Vera central processing unit, which he previously described as providing access to a market opportunity worth approximately $200 billion. Nvidia stated that organizations including OpenAI, Anthropic, and SpaceX are among the early adopters evaluating the technology.

The Computex presentation also featured discussion about the future direction of artificial intelligence across the computing industry. Qualcomm Chief Executive Officer Cristiano Amon, speaking separately ahead of the event, argued that the industry is moving beyond AI systems that simply generate responses to prompts and toward software capable of carrying out tasks independently. He described 2026 as a potential turning point for agent-based AI, adding that existing device architectures were largely designed around actions initiated by users rather than autonomous software systems.

Huang also addressed concerns that advances in artificial intelligence could reduce employment opportunities for software developers. Rejecting that view, he argued that AI tools are increasing productivity and enabling organizations to undertake larger software projects, which in turn could create additional demand for engineering talent.

The announcements come as Nvidia continues to expand its presence across multiple segments of the AI market. After becoming one of the leading suppliers of hardware for AI model training, the company is now seeking a larger role in personal computing, inference processing, and AI applications designed to run directly on consumer devices.

The developments were unveiled in Taiwan, a location Huang described as central to the global AI supply chain. The Nvidia chief, who was born in the southern Taiwanese city of Tainan, has repeatedly emphasized the island's importance to the future development and production of advanced computing technologies.

Hackers Attack Sugar Mill, Force Operations and Harvesting Shutdown



 

Sugar Mill

Cloud Cyber Security Data Breach Harvesting Internet Sugar Mill

Hackers Attack Sugar Mill, Force Operations and Harvesting Shutdown

Australia’s second-biggest sugar producer, Mackay Sugar, is looking into a cyberattack that impacted parts of its operations and temporarily stopped sugarcane harvesting.

The incident caused the stoppage of milling activities at two of the firm’s facilities while authorities and experts tried to assess the disruption of the attack.

In a recent statement, Mackay Sugar acknowledged the cyberattacks and disruption impacting few of its operations.

The immediate priorities are ensuring staff safety, continuing business operations safely, and safeguarding operational systems. “Our immediate focus is the safety of our people, protecting operational systems, and maintaining business continuity,” it said.

About risk assessment

Mackey Sugar is also working with authorities to inspect the incident and recover impacted systems safety.

The incident directly impacted production operations. Local media reports have hinted that the company was compelled to close down its Racecourse and Farleigh sugar mills, two key facilities based in Queensland’s Mackay area. This caused the growers to stop harvesting sugarcane until notified.

The impact on production

The group also verified that the Farleigh and Racecourse mills' cane hauling and sugar milling operations had been halted. Shortly after both facilities started their yearly sugarcane crushing season, there was an interruption.

Although many growers in the area have been impacted by the closure, producers in the Marian district have not been immediately impacted. The district's third mill for Mackay Sugar is not expected to start up until next week, according to a report from Australia's ABC News.

While recovery efforts continue, the sugar producer said it has put in place temporary measures and interim procedures to support critical business operations and minimize operational impact.

Mitigation processes

According to the company, "interim procedures are in place to support critical business functions and minimize disruption where possible."

Additionally, the company stressed that throughout the event, it is staying in touch with growers, staff, and business partners.

"We will continue to provide updates as more information becomes available and are in direct communication with our employees, growers, and key partners," Mackay Sugar stated.

About recovery

Mackay Sugar acknowledged the anxiety brought on by the disruption and reaffirmed that company takes cybersecurity duties seriously.

"We take extremely seriously our obligation to safeguard our information, operations, and systems. We will give timely updates as we complete our inquiry, and we apologize for any inconvenience or uncertainty this incident may have caused," the business stated.

Cyberabad Police Busts eSIM Banking Fraud Gang in Hyderabad



 

User Security

Cyber Fraud Cyberabad Police eSim Scam Sim Swapping User Security

Cyberabad Police Busts eSIM Banking Fraud Gang in Hyderabad

Cyberabad police have exposed an inter-state cyber fraud racket that used eSIM manipulation, SIM swapping tactics, and OTP diversion to steal money from bank customers. The case underlines how criminals are mixing telecom fraud with banking deception to bypass normal security checks and move money fast.

Investigators said the accused impersonated staff from a bank’s premium credit card division and contacted victims under the guise of DoT verification. They persuaded targets to convert eSIMs into physical SIM cards, then sent preloaded mobile devices carrying malicious apps, which helped redirect OTPs and banking alerts to the fraudsters.

Once the OTPs were diverted, the gang could access bank accounts, authorize transfers, and siphon off funds before the victims understood what had happened. Police said six people were arrested in the case: Selim Mondal, Abdul Alim SK alias Mittu, Saiyad Hasim Reza alias Tippu, Mijanur Rahaman Shaik, Bansidhar, and Mehebub Alam Ansary alias Suraj. The fraud amount was put at Rs 77.75 lakh, and police recovered Rs 15 lakh in cash during searches at the accused persons’ homes.

The bigger concern is that this type of scam is highly scalable. It does not depend on hacking a bank’s servers; instead, it exploits human trust, weak verification habits, and the phone number as a security key. If a criminal gets control of your SIM or eSIM flow, they may also gain access to banking apps, password resets, and other sensitive services that rely on SMS verification.

Mitigation tips

To stay safe from this type of eSIM banking fraud, never share OTPs, PINs, card details, or recovery codes with anyone over call, SMS, or WhatsApp, even if the caller claims to be from a bank or telecom company; verify any eSIM or SIM change request only through your operator’s official app, website, or helpline; avoid clicking suspicious links or scanning unknown QR codes.

Additionally, do not insert a SIM into any courier-delivered or unfamiliar device; enable banking alerts, use strong passwords and authenticator apps instead of SMS-based verification where possible; and if your phone suddenly loses signal or you suspect a SIM hijack, immediately contact your mobile provider, freeze transactions with your bank, and report the issue through India’s cybercrime helpline 1930 or the official cybercrime portal.

ShinyHunters Exploits Oracle PeopleSoft Zero-Day to Breach Universities and Enterprise Systems



 

Enterprise Security Risks

CVE CVE vulnerability Cyber Attacks Cybersecurity Threats Data Breaches enterprise cybersecurity Enterprise Security Risks

ShinyHunters Exploits Oracle PeopleSoft Zero-Day to Breach Universities and Enterprise Systems

A breach tied to the hacking collective ShinyHunters emerged during a wave of intrusions leveraging an undisclosed weakness in Oracle PeopleSoft platforms. Unauthorized entry occurred because security gaps went unpatched - access followed swiftly after initial compromise. Data theft unfolded across multiple campuses and research-focused entities throughout May into June's first days. Evidence gathered by Google Cloud Mandiant analysts pointed directly toward systemic exploitation prior to any public alert from Oracle. Control over affected servers enabled extraction of confidential information before patches were available.

One security team links these actions to a hacking cluster known internally as UNC6240. Exploiting a weakness labeled CVE-2026-35273, they triggered unauthorized code on Oracle PeopleSoft systems. This issue sits near the top of risk scales - rated 9.8/10 - given how easily it can be abused. With nothing more than an open HTTP connection, intruders bypass login checks entirely. Access unfolds remotely; no clicks or credentials required by victims.

Within the PeopleSoft platform, the weakness lies specifically in the Environment Management Hub. Though Oracle officially acknowledged issues in PeopleTools 8.61 and 8.62, earlier versions - no longer supported - could still face risks. Because exploitation began prior to Oracle's public notice, the vulnerability acted like a real zero-day during the entire attack period. Hidden weaknesses emerged when hackers mistakenly left key systems visible on the web.

A closer look revealed open servers storing malware frameworks, communication hubs, admin utilities masked as legitimate cloud documents, along with automation codes designed to navigate internal corporate environments. Spread through connected devices began once access was gained, followed by bundling sensitive material before sending it toward platforms tied to ShinyHunters’ operations. Mandiant found over 100 groups facing possible system exposure, alerting each to the danger. Higher education made up close to 68% of these cases, primarily within the U.S.

While certain schools stopped threats in time, several faced verified intrusions alongside leaked information. Among the earliest cases made public stood the University of Nottingham. Reports tracking data leaks indicate the exposed records include around 455,000 distinct email addresses, followed by private details such as full names, residential locations, telephone numbers, passport identifiers, ethnic background, and data tied to disabilities. Confirmation of the event came directly from the institution itself.

Turning off the Environment Management Hub service is a step Oracle suggests when feasible, while limiting outside connections to vulnerable endpoints. Experts in cybersecurity point out that checking system logs matters, along with hunting down odd-looking files. Uncommon patterns in data leaving the network should catch attention. Applying fixes from Oracle promptly stands as another measure worth taking.

Surprisingly, ShinyHunters once stuck to phishing, compromised logins, or manipulating people through psychological tricks. Now, though - using a previously unknown flaw in server software suggests their methods have taken a sharper turn. This shift hints at ERP platforms being eyed more closely going forward, even if nothing is certain yet.

OpenClaw Security Flaws Expose AI Agents to Hidden Commands and Data Theft Risks



 

Vulnerabilities and Exploits

AI Agent Security AI Phishing Attacks OpenClaw security vulnerability prompt injection attack Vulnerabilities and Exploits

OpenClaw Security Flaws Expose AI Agents to Hidden Commands and Data Theft Risks

Two independent cybersecurity studies published this week have uncovered serious security weaknesses in OpenClaw, a widely used self-hosted AI agent platform. The findings demonstrate how attackers can manipulate AI agents into executing malicious code or leaking sensitive information through seemingly harmless inputs.

Researchers from Imperva and Varonis approached the issue from different angles but reached a similar conclusion: AI agents that trust incoming data and possess broad system access can become powerful attack vectors when exploited.

Hidden Instructions Embedded in Everyday Content

Imperva researchers discovered that OpenClaw could be tricked into processing concealed instructions embedded within shared contacts, vCards, and location pins. These malicious commands were executed by the AI agent without any visible indication to the user.

The issue stemmed from how OpenClaw handled certain message objects before passing them to the large language model (LLM). While content fetched from the web was clearly marked as untrusted, information contained within contacts, vCards, and location labels was inserted directly into prompts without any trust boundary.

According to Imperva researcher Yohann Sillam, this allowed attackers to hide instructions inside fields such as contact names. Since angle brackets are permitted in contact names, the model could not reliably distinguish legitimate information from injected commands.

Only selected fields were transmitted to the model, making them attractive targets. In one example, a shared contact was serialized as <contact: name, number>, allowing attackers to insert malicious instructions within the name field itself. Because messaging apps truncate long contact names, victims often never saw the hidden payload.

The same attack method was also successful through WhatsApp-supported vCards and shared location labels.

During testing against Gemini 3.1 Pro's preview build, hidden instructions successfully convinced the AI agent to download and execute a script hosted on servers controlled by the researchers. Similar attempts using images with embedded instructions failed, likely because AI models have become more resistant to that well-known attack technique.

Imperva warned that OpenClaw's default memory functionality could amplify the threat. A single malicious piece of widely shared content could potentially affect multiple agents if adequate sandboxing protections were absent.

Following responsible disclosure, OpenClaw addressed the issue in version 2026.4.23. The update separates contact names, vCard information, and location labels from the main prompt and places them in an isolated untrusted metadata channel.

Researchers also noted that similar design patterns exist in several other personal AI assistant platforms, suggesting the issue extends beyond OpenClaw alone.

Social Engineering Defeats Technical Safeguards

While Imperva focused on prompt injection, Varonis Threat Labs explored how AI agents respond to social engineering attacks.

Led by researcher Itay Yashar, the Varonis team created an OpenClaw-based agent called Pinchy and connected it to a Gmail inbox filled with realistic business communications and synthetic sensitive information. The researchers then tested the agent using four different phishing scenarios involving Google Gemini 3.1 Pro and OpenAI Codex GPT-5.4.

Varonis distinguishes traditional prompt injection from what it calls "agent phishing." Unlike hidden instructions embedded in content, agent phishing relies on convincing requests delivered through normal communication channels, exploiting the agent's willingness to act before verifying legitimacy.

The tests revealed significant weaknesses.

In one scenario, an email impersonating a team leader named Dan requested urgent staging access during a simulated production emergency. The message originated from an external Gmail account, yet the agent located and forwarded mock AWS IAM access keys, database connection credentials, and SSH details in plain text.

A second phishing attempt used a more routine business request, asking for a weekly customer export supposedly needed for a QBR presentation. The agent responded by sending a synthetic database containing information on 247 enterprise customers, including contact details and contract values.

Notably, these failures occurred despite the agent being configured with instructions to verify sender identities before responding. Researchers observed that urgency successfully bypassed safeguards in one case, while routine business language defeated them in another.

The agent demonstrated stronger performance against technically oriented threats. It interacted with a phishing page designed to steal gift-card credentials but ultimately withheld sensitive information and flagged suspicious behavior. A stricter configuration blocked the page entirely.

Similarly, when presented with a malicious OAuth consent screen disguised as a timesheet application, the agent examined the redirect destination, recognized warning signs, and refused access.

Researchers concluded that AI agents may outperform many users when identifying suspicious URLs and fraudulent login portals. However, they remain vulnerable to social manipulation that exploits helpfulness and trust.

Varonis also observed that OpenAI Codex GPT-5.4 behaved more cautiously than Gemini 3.1 Pro when interacting with external websites or transmitting data. Nevertheless, both models ultimately fell victim to the social-engineering scenarios.

One Core Problem Behind Multiple Attacks

Varonis linked both attack methods to what researcher Simon Willison describes as the "lethal trifecta": an AI system capable of accessing private data, consuming untrusted content, and transmitting information externally.

OpenClaw satisfies all three conditions, making both hidden prompt injections and phishing-based attacks highly effective.

Additional concerns emerged from a separate InfoSec Write-ups analysis. Researchers converted historical OpenClaw security advisories into static-analysis rules and uncovered five additional vulnerabilities affecting integrations with Slack, Discord, Matrix, Zalo, and Microsoft Teams.

Each flaw originated from the same design issue. Channel allowlists were validated using mutable display names rather than permanent identifiers. Attackers could therefore impersonate trusted users simply by changing their display names to match approved accounts.

OpenClaw has since patched these vulnerabilities.

The platform's extensive permissions—including access to files, shell environments, and more than twenty messaging services—have previously prompted warnings regarding prompt injection and data exfiltration risks.

The strongest criticism came from the Dutch data protection authority, the Autoriteit Persoonsgegevens, which advised users and organizations against deploying OpenClaw on systems containing sensitive information due to concerns over data breaches and account compromise.

Recommended Defenses

Organizations using OpenClaw are advised to upgrade immediately to version 2026.4.23 or newer to mitigate the message-object vulnerability identified by Imperva.

However, researchers stress that software updates alone cannot solve the broader trust problem inherent in autonomous AI systems.

Varonis recommends four key safeguards:

Treat agent instruction files as strict, version-controlled policies rather than informal guidance.
Require approval before agents send messages to unfamiliar recipients, reducing the risk of automated phishing or data leakage.
Restrict access to connected systems based on the trustworthiness of the triggering source.
Require human review for high-risk actions such as credential sharing, financial transactions, or sensitive data transfers.

Both research teams ultimately advocate the same mindset. Varonis recommends treating AI agents as inexperienced employees with extensive system access but limited judgment, while Imperva describes them as authenticated executors that inherently trust incoming information.

Although vendors continue to introduce patches and protective controls, the fundamental challenge remains unresolved. AI agents derive their usefulness from acting on instructions, processing inputs, and helping users accomplish tasks. Those same characteristics also create opportunities for attackers, and the industry has yet to develop a universal solution.

Search This Blog

Sections

Popular Posts

Blog Archive

Labels

About Me

Footer About