Search This Blog
Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Load More
Trendy Right Now

Popular Posts

Latest News

Russia-Aligned Hackers Target Ukraine's War Crimes Courts and Military Aid Networks

  A Russia-aligned hacking group that researchers had not previously named or documented has been running a systematic intelligence campaign...

All the recent news you need to know
Sensitive Business Data
AI Data Exposure AI Security Artificial Intelligence Security Cloud Security Data Breach Data Privacy Microsoft Azure Misconfiguration Private Chat Logs Sensitive Business Data

Over 18 Million Files Leaked in AI Aggregator Breach, Raising Privacy Concerns


There has been a major data exposure at the AI aggregator 302.ai that has resulted in millions of documents containing private user conversations, personal information and confidential business material becoming publicly accessible. 


Cybernews cybersecurity researchers discovered an unsecured Microsoft Azure storage bucket belonging to this platform, which exposed approximately 22.72 terabytes of information. There were 17.6 million files in the exposed archive, including images, videos, audio recordings, documents and chat histories. The storage bucket was publicly accessible without password protection or encryption, resulting in anyone able to discover its location having access to the information stored there. 

302.ai is a platform that facilitates the interaction between users and a variety of artificial intelligence services, enabling customers to access multiple large language models on one platform. In addition to ChatGPT, Claude, Grok, DeepSeek, and Gemini, the company supports ChatGPT, Claude, Grok, and Gemini. This arrangement permits users to switch between artificial intelligence models without having to access each provider separately. 

According to Cybernews, the exposed storage contained approximately 144,000 JSON-formatted conversation logs. Users' prompts, AI-generated responses, models used to process requests, timestamps, token consumption costs, and other related metadata were part of these records. As part of the conversations, users entered personally identifiable information as they interacted with the platform. 

The records included details about their birthdates, genders, names, contact information, and addresses, among other personal information. A combination of such information and conversation histories and uploaded documents can reveal more details about individuals than their ordinary chatbot activity. The exposure was more extensive than text-based communications.

The archive contained more than 9 terabytes of images, 7.7 terabytes of videos, and another 5.6 terabytes of audio files. The researchers also discovered over 26,000 ZIP archives containing conversation summaries, inputs from users, AI responses, and attachments to individual sessions. According to reports, a number of documents within the storage were related to large language model development research projects and materials reportedly submitted for private analysis. It is evident from the findings that the information exposed was not confined to individuals, but included information related to business activities as well. 

An especially sensitive discovery involved multiple conversations with a chatbot that provided customer support for a prominent manufacturer of sex dolls. These records illustrate the increasing use of third-party artificial intelligence platforms to manage enterprise customer interactions, resulting in potentially exposing confidential and personal information to external storage environments. Cybernews failed to identify the manufacturer or determine whether all of its customer-service records were exposed. 

Despite the discovery, other concerns have been raised regarding the handling of sensitive customer conversations by third-party artificial intelligence services. As opposed to a confirmed cyberattack, researchers stated that the exposure was likely the result of an accidental storage configuration error. Nonetheless, the investigation did not determine whether any unauthorised parties accessed the files prior to the security measures being implemented or if the technical cause could be determined.

The exposed Azure storage was discovered on August 2, 2026, as reported by Cybernews. A team of researchers contacted 302.ai on August 11 and observed that public access had been disabled by September 8. Researchers found no evidence of malicious actors downloading the information, however it was not impossible for unknown parties to obtain access.

Exposed AI Conversations Could Enable Targeted Cyberattacks

Cybercriminals might be able to conduct targeted phishing and social engineering campaigns if these information is obtained by malicious individuals. As a result of chat histories revealing personal details, business relationships, ongoing projects, customer concerns, and other information, attackers are able to make fraudulent communications appear more convincing by using this information. 

Conversations between employees, customers or senior management could be particularly useful for impersonation attempts. An attacker could also use information contained in uploaded documents and interactions with chatbots to identify potential targets and gain an understanding of internal company operations. The incident demonstrates the security risks associated with third-party AI aggregators. 

In addition to providing access to models developed by major technology companies, platforms such as 302.ai also maintain their own infrastructure to handle prompts, conversation histories, and uploaded files. Generally, the security protections offered by the underlying AI providers do not extend to third-party intermediaries. 

Businesses Urged to Review AI Data Handling Practices

For organizations that rely on artificial intelligence platforms to process customer inquiries, internal documents, and other confidential information, the exposure raises significant concerns. Companies using 302.ai should identify which employees and departments have used the service and whether sensitive company information or customer information has been shared. 

A security team should also review all available conversation histories and uploaded files for potential vulnerabilities in credentials, API keys, and confidential documents. Credentials discovered in submitted materials should be rotated, while suspicious account activity should be investigated. In light of the incident, it is important to evaluate third-party AI vendors before incorporating them into business workflows.

Providers should be examined to determine how they restrict access to storage, protect uploaded files, separate customer information, and manage data retention and deletion. 302.ai is developed by Univerads Technology Limited, a Hong Kong-based company founded in 2020. This exposure illustrates how weaknesses in intermediary platforms can result in sensitive information being compromised, even when the AI models accessed through those services are operated by established technology companies.

It is clear from the 302.ai exposure that there are growing security concerns associated with third-party artificial intelligence platforms and sensitive data they handle. Businesses are increasingly integrating artificial intelligence tools into their operations; however, preventing confidential information from being made public requires strong data protection measures, regular security assessments, and thorough vendor evaluations.
Read more »
Spyware
Android APT29 Cyber Attacks iOS Spyware

APT29-Linked Campaign Uses Compromised Websites to Target iOS and Android Devices


Russia-linked cyberespionage hackers have compromised a legitimate web analytics script to distribute sophisticated spyware targeting Apple iOS and Google Android devices. The campaign, named Poisoned Source, uses malicious JavaScript injected into trusted websites to identify visitors' devices and deliver exploits designed to steal sensitive information.

The operation has been linked to APT29, a cyberespionage group associated with Russia's Foreign Intelligence Service (SVR). According to cybersecurity researchers, the attackers abused a third-party web analytics service to reach visitors of legitimate websites without requiring them to download suspicious applications or files.

Attackers use three infection methods

According to Sekoia researchers Amaury-Jacques Garçon and Félix Aime, the campaign relied on three main methods to infect devices. These included compromising legitimate websites, creating fake websites that impersonated well-known organisations, and conducting a supply-chain attack against Plerdy SEO Tracker.

The supply-chain compromise took place between August 27 and September 3, 2026. During this period, attackers injected malicious code into the JavaScript file hosted on Plerdy's infrastructure. Since the analytics script was used by thousands of websites, the compromise potentially exposed a large number of visitors to the malicious code.

The researchers discovered that the attackers also created lookalike websites impersonating organisations in the United States, Ukraine, the Czech Republic and Bulgaria. Some compromised websites were associated with the chemical industry, political organisations and military-related activities.

Exploits target iOS and android devices

Once the malicious JavaScript executes, it collects information about the visitor's browser, operating system and device configuration. 

For Apple devices, the attackers used the DarkSword exploit kit to target vulnerable iOS versions. Depending on the device, the malware could steal Safari cookies or extract more extensive information, including text messages, WhatsApp and Telegram databases, contacts, call history, photographs, Wi-Fi passwords and iCloud Keychain data.

Android users were targeted through a separate malware payload called AndroSnitch. The attack exploited vulnerabilities in Google Chrome to gain access to the device and collect browser information, including cookies, saved login details and Wi-Fi passwords.

Researchers identified several security vulnerabilities used in the campaign, including CVE-2025-43529, CVE-2026-20700 and CVE-2026-3910. These vulnerabilities allowed attackers to execute malicious code and bypass security protections on vulnerable devices.

Targeted espionage warning

Sekoia said the campaign appeared to focus on websites likely to attract strategically important visitors, particularly those connected to military organisations and defence-related industries.


Read more »
WordPress Core
CISA Security Patch Vulnerabilities and Exploits WordPress Core

CISA Warns of Actively Exploited WordPress RCE Flaw

 

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has warned that attackers are actively exploiting a recently patched, high-severity vulnerability in WordPress Core. The flaw, tracked as CVE-2026-119977, can allow unauthenticated remote attackers to execute code on affected servers. CISA added the vulnerability to its Known Exploited Vulnerabilities (KEV) Catalog and ordered federal civilian agencies to address it by Friday under Binding Operational Directive 26-04. The warning highlights how quickly attackers move from public patch information to real-world exploitation. 

The vulnerability is caused by a Time-of-check Time-of-use (TOCTOU) race condition in WordPress’s upgrade process. It was reported by Picus Security researcher Umut Bayram and relates to predictable, web-accessible staging paths used during full-package core upgrades. During the upgrade window, an attacker may be able to interfere with the process and achieve remote code execution. Although exploitation is described as high-complexity, the potential impact is serious because successful attacks do not require prior privileges on the server. 

WordPress released version 7.1.4 on October 28 to fix the issue, urging administrators to update their sites immediately because it was a security release. CISA later confirmed evidence of active exploitation and emphasized that such vulnerabilities are a frequent attack vector for malicious cyber actors, posing significant risks to the federal enterprise. While the federal directive applies only to U.S. federal agencies, CISA also urged private-sector organizations and other network defenders to prioritize patching their WordPress installations. 

The scale of attempted attacks appears substantial. According to WordPress security firm Wordfence, it blocked 13,095 attacks targeting the vulnerability within a 24-hour period. CISA has not publicly disclosed detailed information about the threat actors, targets, or post-exploitation activity. Even so, the volume of blocked attacks suggests that adversaries are scanning broadly for vulnerable WordPress sites rather than focusing on a small number of high-value targets. 

The incident follows earlier WordPress security concerns, including the “wp2shell” vulnerability chain patched in July. That chain combined a REST API batch-route confusion flaw and an SQL injection vulnerability to deploy webshells and take over unpatched servers. Public exploit code appeared shortly after the fix, and attackers later used the technique to install malicious plugins and steal database records. Together, these cases reinforce an essential lesson for site owners: apply WordPress core and plugin updates promptly, restrict administrative access, monitor upgrade activity, and maintain reliable backups to reduce the impact of exploitation.
Read more »
SSH keys
api tokens Linux Backdoor malware OPSSHIELD SSH keys

cPGuard Update Channel Hijacked to Deploy Linux Backdoor and Steal Server Credentials

 




A cyberattack targeting OPSSHIELD's software distribution infrastructure allowed an unidentified attacker to compromise cPGuard updates and deploy a malicious script across customers' Linux servers, harvesting password hashes, SSH keys, database credentials, and other sensitive information.

The incident began on November 2, 2026, when the attacker exploited compromised credentials to access OPSSHIELD's update distribution infrastructure. According to the company's investigation, approximately 2,950 customer servers executed the malicious update, while nearly 7,900 billing portal account records were also exposed.

cPGuard, OPSSHIELD's Linux server security solution, provides malware scanning, firewall management, and attack protection for web hosting environments, including servers running cPanel, DirectAdmin, and Plesk.


Compromised Update Infrastructure Delivered Malicious Script

OPSSHIELD's investigation traced the intrusion to its billing and licensing application. The attacker initially registered a customer account under a false identity on November 1 and requested a free cPGuard trial to examine communications between the software and its licensing infrastructure.

After probing the billing portal and submitting specially crafted requests, the attacker obtained command execution on the company's billing and licensing server. This access enabled the theft of credentials used to distribute software updates.

Between 02:04 and 02:09 UTC on November 2, the attacker uploaded a malicious update using a stolen access key. The compromised versions, ranging from 5.88.12 through 5.88.19, were distributed for approximately 70 minutes and executed with root privileges on servers checking for updates during that period.

OPSSHIELD detected the compromise within 12 hours and subsequently revoked the stolen update key.


Password Hashes and SSH Credentials Targeted

The malicious script collected sensitive system information and transferred it to OPSSHIELD's licensing infrastructure through a compromised account, allowing the attacker to retrieve the uploaded data.

The targeted files included "/etc/shadow" and "/etc/passwd", root's MariaDB/MySQL configuration ("my.cnf"), shell history, and SSH authorization and known-hosts files. The script also accessed root's SSH private keys and cloud storage credentials on some systems.

The "/etc/shadow" file contains password hashes rather than plaintext credentials. However, attackers can attempt offline password cracking against these hashes, particularly when passwords are weak, commonly used, or previously exposed. Database configurations and shell histories may contain credentials and API tokens that are immediately usable without requiring password cracking.

OPSSHIELD initially confirmed that attackers retrieved 32 collected files, each associated with a different customer server. Its subsequent disclosure estimated approximately 2,950 servers executed the malicious update.

The attackers also copied approximately 7,900 billing portal records containing customer names, company information, postal addresses, email addresses, and bcrypt-hashed passwords.


OPSSHIELD Releases Security Updates

The malicious script left several identifiable artifacts, including "cpguard-v58812-i91511.sh", a hidden root shell at "/var/tmp/.cpg91511_sh", and a collection directory at "/var/tmp/.cpg91511", containing the staged archive "loot.tgz".

OPSSHIELD's corrective updates remove the known backdoor and associated malicious files. However, removing these artifacts does not establish that a server was never compromised.

The company initially recommended updating to version 5.88.25 or later. Its subsequent disclosure identified version 5.88.26 as the clean release, which also addresses additional persistence mechanisms.

Administrators should run "cpgcli update --start" and verify the installed version using "cpgcli --version".

For potentially affected systems, OPSSHIELD recommends resetting local account passwords, rotating database credentials, S3 access keys, DigitalOcean tokens, and other exposed secrets. Administrators must also replace root SSH private keys and remove corresponding public keys from systems that previously trusted them.

Customers should additionally reset their OPSSHIELD billing portal passwords and enable two-factor authentication.

OPSSHIELD has also begun revoking its previously deployed support-access keys and rebuilding compromised internal infrastructure. Although the company initially did not recommend routine operating system reinstalls, its updated disclosure confirms that affected customer servers are being rebuilt where necessary.

Read more »
Cyber Security Ransomware Attacks
AI cyberattacks AI cybercrime AI Risks AI technology Cyber Attacks Cyber Researchers Cyber Security Ransomware Attacks

UK School Network Hit by 3AM Ransomware as Researchers Suspect AI-Assisted Intrusion

 

An incident involving ransomware against a UK school network has brought attention to how much of a factor AI is becoming in cybercrime. During the attack, an affiliate running 3AM ransomware utilised an unmanaged host to gain access to nearly half of the machines (encrypting approximately 37). 

This was discovered by Bitdefender. There were multiple indications during the investigation into the attack that AI could have been involved. There were multiple instances where the attacker was running similar commands with slight modifications between each run. These commands had approximately 40-100 second gaps between them. This could be seen as an automated agent, whereby the system would create commands, assess the outcome and adapt the next command. 

Bitdefender cannot confirm there was any involvement from a language model. As the machine the attacker was using could not be looked at by researchers, there is no way to confirm what model was used, or if it was local or remote. This is a purely an observation. The attack occurred between 10th and 19th of September. The initial method of gaining access is unknown. The attacker focused on gaining credentials and expanding their access. They used a modified public PowerShell tool to extract and decrypt credentials from 3 Veeam backup servers. They also extracted a Chrome database containing saved login information. 

Mimikatz and LSASS memory extraction tools were also deployed. The attacker also carried out further reconnaissance. They looked at domain relationships and searched login script folders to find any mention of other schools. They created 2 domain admin accounts called ‘library’ and ‘svc_bkpmon’ to give themselves persistence. Financial data was also extracted from the compromised machines. The attacker then created 2 way trust relationships between 3 previously separate Active Directory domains. 

Finally they attempted to disable endpoint protection. Sophos and Bitdefender were targeted for removal. System state backups were also targeted for removal. The affiliate then deployed the Rust based encryption tool from 3AM, impacting around 37 machines. 3AM first came to light in 2023 after being used by an attacker when LockBit was blocked. It has been linked to Conti and Royal ransomware gangs. 

The affiliates have been linked to Email Bombing and pretending to be IT support via spoofed calls. This group has previously been linked to major data leaks. Kootenai Health revealed an incident in August 2024 where personal data from over 464,000 patients was compromised. This investigation by Bitdefender shows there is concern around ransomware actors experimenting with AI assisted methods. 

Whilst it is unclear exactly how much AI was involved in this incident, this comes at a key time as the National Cyber Security Centre in the UK has released their annual ‘The State of the Cyber Nation’ report. They are urging organisations in critical infrastructure to be prepared for AI driven ransomware threats by 2028.
Read more »
Webshell Attacks
Active Cyberattacks Critical security flaw CVE-2026-58115 IOT Security Linux Bot Malware Node-RED Vulnerability Remote Code Execution Vulnerabilities and Exploits Webshell Attacks

Attackers Leverage Critical Node-RED Flaw to Gain Unauthorized Access


There is an active exploit of a critical security vulnerability in Node-RED by threat actors to install malicious Linux bots and webshells on vulnerable systems. It is believed that the attacks, detected by cybersecurity firm VulnCheck, could result in compromised instances and industrial environments being exposed to remote command execution and unauthorized access. 

Tracked as CVE-2026-58115, the vulnerability has a CVSS severity rating of 10.0. Node-RED HTTP interface does not contain authentication, allowing remote attackers to access programming functions and execute system commands on the underlying server if unauthenticated remote attackers are not authenticated. 

A browser-based editor enables users to build event-driven applications using Node-RED, an open-source, flow-based programming tool. It is widely used in industries including manufacturing, healthcare, home automation, and industrial control systems. A number of Siemens IoT2050 Advanced devices have been integrated with the platform, including Siemens SIMATIC IoT2050 Advanced devices.

Siemens disclosed the vulnerability on August 11, 2026, after identifying the issue with SIMATIC IoT2050 Advanced devices running Industrial OS with Node-RED installed. In order to take advantage of this vulnerability, attackers could create malicious programming flows and execute arbitrary code with maximum privileges if it is successfully exploited.

A fix for the vulnerability is available in Siemens SIMATIC IoT2050 Advanced version 4.3.4.1 and later. Although security updates have been available, attackers continue to target vulnerable instances. A malicious request containing a complete exploit was captured by one of VulnCheck's monitoring systems on October 30, when it was detected as successful exploitation. This attack deployed a Node-RED flow, triggered its execution automatically, and downloaded a binary from a server controlled by the attacker. 

A malicious execution flow was initiated using Node-RED components, including the inject and execute nodes, without requiring additional interaction from the attacker. There has been no indication of the exact purpose of the downloaded binary, identified as bot-linux-amd64, which was stored under a hidden filename in a memory-backed location and executed in the background. 

Researchers were unable to retrieve the binary for further examination. During the exploitation campaign conducted between October 30 and November 1, repeated attempts were made from the same IP address. The attack vectors used by VulnCheck are 16 attempts to exploit CVE-2026-58115, with attackers delivering a variety of payloads across multiple requests. 

The address used by the attackers originates from Microsoft's AS8075 network, which is located in Brazil. A researcher cautioned that the use of cloud providers' networks does not necessarily identify threat actors, since such infrastructure may include virtual machines rented or compromised by cloud providers. Other attempts were made to install webshells, which gave attackers access to compromised servers and the ability to execute commands remotely, in addition to deploying Linux bots.

In some instances, additional shell scripts and files appeared to be legitimate Linux kernel processes. As opposed to the originally observed bot, which was stored in memory and could be removed when the system was rebooted, the webshells provided a more persistent method of access. In addition to identifying broader scanning activity from the same IP address, VulnCheck also recorded 125 requests targeted at eight different vulnerabilities affecting Apache Solr, Camunda, Gitea, MLflow, Traefik, and Joomla. 

A survey of Node-RED installations indicates opportunistic mass scanning rather than activity concentrating exclusively on Node-RED installations Security experts have expressed concerns about the vulnerability of industrial environments through poorly secured Node-RED deployments. 

Industrial controllers are often integrated with databases, messaging systems and cloud services through this platform, allowing the platform to hold credentials for multiple connected systems. Consequently, a compromised instance could give attackers access beyond the initial server and facilitate movement across networks in the areas of information technology and operational technology. It is also important to note that Node-RED deployments are not always managed by dedicated IT security teams, increasing the risk. 

It is common for engineers and operational staff to configure Node-RED installations directly, thus preventing regular asset inventories and security monitoring. Additionally, scheduled maintenance requirements can delay firmware updates in industrial environments, resulting in vulnerable devices remaining exposed even after patches have been released.

CVE-2026-58115 has been added to VulnCheck's Known Exploited Vulnerabilities (KEV) catalog in response to the observed attacks. When reported, this vulnerability was not listed in CISA's KEV catalog. It is recommended that organizations using Node-RED apply security updates, enable authentication via the adminAuth setting, and restrict external network access to the editor. 

The security team should also examine deployed flows for unanticipated executable nodes, unauthorized HTTP endpoints, and suspicious file modifications. It is equally important to examine system logs and outbound network connections for signs of compromise, as installing patches alone may not remove webshells or other malicious components already present on the system.

Node-RED deployments exposed to industrial environments may pose security risks resulting from the active exploitation of CVE-2026-58115. It is recommended that organizations prioritize patching, enforce authentication, limit access to the editor and investigate for signs of compromise. In light of the possibility of existing webshells remaining after updates have been applied, security checks should accompany remediation efforts as well.
Read more »
Subscribe to: Posts (Atom)

Featured