Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Japanese Homeware Giant Iris Ohyama Says Cloud Breach at Its Online Store May Have Exposed Data of Up to 7.7 Million Shoppers

 



Iris Ohyama, one of Japan's most recognized consumer goods manufacturers, has disclosed that a third-party cloud service used by its online shopping platform was accessed without authorization, potentially exposing personal data belonging to roughly 7.7 million people, including customers who never created an account.

The company, founded in 1971 and headquartered in Sendai, is best known for plastic storage solutions and home appliances sold across Asia, Europe, and North America. Its e-commerce platform, Iris Plaza, caters to millions of customers in Japan and handles a large volume of household product purchases. The scale of the breach puts it among the larger data security incidents Japan has seen this year, in a period when Japanese companies and government agencies have dealt with a string of serious intrusions.


How the Breach Was Detected

On October 28, 2026, Iris Ohyama staff detected suspicious files inside a cloud service that Iris Plaza relies on for its operations. The company did not name the cloud provider or describe the method the attacker used to get in. Within a day, the company suspended access to Iris Plaza and related systems, reported the incident to Japan's Personal Information Protection Commission, and filed a report with police.

A follow-up disclosure on November 5 gave a clearer picture of the scope: up to 5.8 million registered and former members may have had their data accessed, along with up to 1.9 million non-members, meaning people who had completed a guest checkout without registering. The fact that guest buyers are part of the exposure is insurmountable, since many people assume their data is not retained when they shop without creating an account. In Iris Plaza's case, it was.


What Data Was in the Affected System

The range of information potentially accessed varies depending on the type of account. For registered members, exposed fields can include full name, home address, phone number, email address, gender, and date of birth. Account passwords were also stored in the affected environment, though the company said they were encrypted. It did not specify which encryption method was used, leaving questions open about how resistant those passwords are to cracking.

Former members are in a slightly different position: Iris Ohyama said it does not retain passwords for accounts that have been closed, so that group faces a narrower exposure. For non-members who checked out as guests, the data stored was more limited.

One notable reassurance: the company confirmed that credit card information was not stored in the affected cloud environment, sparing customers from the most immediately damaging form of financial exposure.

As of November 5, Iris Ohyama said it had not received any communication from whoever carried out the intrusion, had not identified any perpetrators, and had not seen reports of fraudulent use or financial damage tied to the breach. The investigation into how many records were actually exfiltrated, as opposed to merely accessible, is still ongoing.


What Iris Plaza Customers Should Do Now

The company has urged customers to change their Iris Plaza passwords and, critically, to change passwords on any other service where they used the same credentials. Password reuse across sites remains one of the most common ways a single breach cascades into wider account takeovers. Anyone who shops with the same email and password combination across multiple retail or financial platforms is at elevated risk.

Iris Ohyama also warned customers to be on guard for phishing attempts. With names, addresses, phone numbers, and email addresses potentially in circulation, attackers have enough to craft convincing messages that appear to come from the company. Iris Ohyama said it will not send emails or SMS messages asking for passwords, PINs, authentication codes, or other sensitive information through links, and customers should treat any such request as fraudulent.


A Year of Costly Data Incidents in Japan

The Iris Ohyama breach lands in the middle of a rough stretch for data security in Japan. This year alone, cloud hosting provider Sakura Internet reported a hack affecting up to 1.36 million accounts, telecommunications giant KDDI disclosed a breach tied to a zero-day vulnerability in third-party software that hit around 12 million accounts across shared email platforms, and Japan's Digital Agency acknowledged that a VPN flaw exposed approximately 246,000 government personnel records. The common thread across several of these incidents is reliance on third-party services and cloud environments where access controls or vendor security fell short.

Iris Ohyama's breach fits that pattern. A third-party cloud provider, an intrusion the retailer only caught when suspicious files turned up, and millions of customer records sitting in an environment the company did not fully control. The investigation remains open, and the company has not said when it expects to restore Iris Plaza to service.



QNAP Urges Immediate Plex2Shell Update and Remediation

 

QNAP has issued a security advisory concerning a vulnerability chain, collectively referred to as Plex2Shell, affecting Plex Media Server installations on QNAP NAS devices. The issue affects Plex Media Server version 1.43.2 and earlier and enables unauthenticated remote code execution when individual flaws are chained together. QNAP has therefore instructed administrators to update Plex Media Server immediately to version 1.43.3, build 1.43.3.10861 or later. 

Technical scope 

Plex2Shell comprises four vulnerabilities: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656. Individually, each issue has a limited security impact, but an attacker can combine them to execute arbitrary code under the privileges assigned to the Plex Media Server process. The vulnerability resides in the third-party Plex application rather than in QTS or QuTS hero. Consequently, QNAP states that its operating systems are not directly affected, and a NAS that does not have Plex Media Server installed does not require remediation.

Affected administrators should navigate to App Center > My Apps > Plex Media Server and select Update. Once the update completes, they must verify in Plex Web under Settings > General that the installed version is 1.43.3.10861 or later. QNAP advises against delaying the update until a later release becomes available. If the update is not visible, administrators should refresh App Center and confirm that the NAS has outbound internet connectivity before attempting the installation again. 

Compromise assessment Updating Plex removes the exploitable condition but does not reverse an intrusion that has already occurred. QNAP states that systems running Plex 1.43.2 or earlier while remotely reachable should be treated as potentially compromised. This exposure applies when Plex Remote Access was enabled, TCP port 32400 was manually forwarded, or the port was exposed through UPnP or myQNAPcloud router configuration. In such cases, QNAP requires a clean reinstall, credential rotation, and a review for indicators of compromise. 

Administrators should inspect running processes for unfamiliar executables launched by Plex, including myawesomeproxy, mylovelyminer, or x12345. They should also examine the Plex Codecs directory for unrecognized .so or .dll files and monitor outbound traffic for connections to proxystream.st. Additional indicators include abnormal CPU utilization when no media is being played and detections produced by QNAP Malware Remover, including signature MR2104. QNAP warns that deleting suspicious files alone is insufficient, since persistence mechanisms may remain; affected systems should follow the full clean-reinstall procedure. 

Secure reinstallation 

For remediation, QNAP recommends preserving the Plex Logs directory if technical support may be required. Administrators should then remove Plex Media Server through App Center, reinstall version 1.43.3 or later, and avoid restoring the previous contents of the Codecs folder. Plex will automatically download required codec components after reinstallation. To reduce recurrence risk, QNAP advises disabling Plex Remote Access when unnecessary, removing port 32400 forwarding rules, disabling UPnP, and using a VPN for legitimate remote access. Administrators should also keep QTS or QuTS hero and all installed applications updated.

Hackers Exploit Third-Party Provider to Steal $133 Million From French Bank


A major French banking group, Crédit Mutuel Arkéa, has suffered a sophisticated cyberattack that allowed hackers to carry out fraudulent financial transactions worth an estimated €118 million ($133 million). 

The attackers reportedly gained access to the bank's network through the platform of an external service provider.

The incident came to light on November 2, when blockchain investigator ZachXBT reported suspicious withdrawals involving several cryptocurrency exchange accounts. According to the investigator, the attackers had potentially stolen around €118 million and moved the funds through cryptocurrency platforms.

Crédit Mutuel Arkéa, one of France's major cooperative banking groups, officially acknowledged the cyberattack on November 4. The bank confirmed that attackers had gained unauthorized access to its systems and used an account belonging to the institution to initiate fraudulent transactions involving other banking organizations.

In a frequently asked questions section published after the incident, the bank explained that the attackers accessed its network directly through the platform of one of its service providers. However, the financial institution did not disclose the identity of the provider. It also clarified that its online banking subsidiary, Fortuneo, was not involved in the attack.

The attackers reportedly used the bank's own account rather than individual customer accounts to transfer the money. Blockchain investigators also tracked the movement of the stolen funds through cryptocurrency exchanges, where some of the money was reportedly converted into stablecoins such as USDC and USDT.

ZachXBT stated that approximately $30 million had already been laundered by November 3. Some of the stolen funds were reportedly blocked, although the complete amount recovered remains unclear. The bank has not independently confirmed the reported $133 million loss, describing the amount involved as significant while acknowledging that the final figure was still being assessed.

After the discovery, Crédit Mutuel Arkéa temporarily suspended certain operations as a precautionary measure while investigating the incident. The bank subsequently announced that the attack had been contained and that its operations were gradually returning to normal.

The financial institution reassured customers that their deposits and personal assets were not affected by the incident. However, some transfer transactions experienced delays because of the security measures introduced in response to the attack.

Arkéa also ruled out human error as the cause, describing the incident as a sophisticated external attack. It is now working with law enforcement agencies and judicial authorities to determine how the attackers gained access and carried out the fraudulent transactions.

Hackers Infiltrate GitHub Projects to Infect Cybersecurity Developers With Advanced Malware

 

Cybercriminals are distributing malware through GitHub repositories designed to look like genuine development projects. Researchers at Doctor Web found malicious code in Microsoft Visual Studio projects, Python scripts and Go files. Over 2000 computers were reportedly infected with this malware. The campaign began around 2 years ago with the initial targets being cryptocurrency users. The repositories were themed around blockchain games, game bots and cheating tools. 

The repositories even included guidance for installing Visual Studio to make them seem more legitimate to less experienced developers. However the malware has now targeted information security professionals. The malicious code is hidden within repositories that claim to be for automated scanning, security testing and log analysis. The infected files have malicious code hidden in the configuration and source code of the repository. The malicious code is hidden with lots of white space. 

When the malicious project is downloaded, it runs PowerShell scripts that fetch further malicious files from external sources. This results in an archive being downloaded containing Microsoft.exe, which is a malware loader built with Electron. The malware has been identified as Trojan.Loader.3261. Once active, the malware gathers information about the system, creates persistence and downloads further payloads. It also tries to disable Windows Defender, User Account Control, alerts and recovery features. 

The malware uses various methods to avoid being monitored by security tools, hijack legitimate windows processes and avoid detection from endpoint detection systems. The malware includes payloads such as BackDoor.AsyncRAT.115 which allows the attacker to remotely access the infected computer. It also includes Trojan.InjectNET.14 which adds a cryptocurrency hijacker to the clipboard. This changes the copied wallet addresses to ones controlled by the attacker. 

It also takes screenshots of the infected system. The malware also includes JS.Stealer.191 which steals information from browsers, VPNs, messaging applications, gaming accounts, FileZilla and Discord. This information is zipped up and sent to the attacker via a Telegram bot. The malware tries to uninstall security tools from ESET, McAfee and Malwarebytes. It also changes the hosts file in windows to prevent access to certain anti virus domains. 

The researchers found multiple variations of how the malware was deployed. They also found other incomplete components which indicates that the malware is still being developed. Future features could include auto reinstall, better persistence, managing applications when they open and updating software. This shows that even information security professionals can be vulnerable to malicious resources. The researchers recommend checking any files you download, keeping anti virus databases up to date and being cautious when cloning unknown GitHub repositories.

Publishers Move Supreme Court Against Key Provisions of Data Protection Law

 


Digital News Publishers Association (DNPA), representing 21 prominent news organizations, has filed suit with the Supreme Court challenging provisions of India's Digital Personal Data Protection Act, 2023, and the DPDP Rules, 2025. As a result of the current data protection framework, journalists could be restricted in their activities, investigative reporting may become complex, and public access to information may be limited. 

Upon receiving notices from the Union Ministry of Law and Justice and Ministry of Electronics and Information Technology (MeitY) on October 27, 2026, the Supreme Court requested the Centre's response to the challenge. This case emphasizes the conflict between preserving the right to maintain an individual's digital privacy and preserving the right to investigate and report issues of public interest for the press. 

Indian Parliament passed the DPDP Act in August 2023, the first comprehensive law specifically designed to protect digital personal data. It establishes rules for organizations and other entities that collect and process personal information. Under the Act, these entities are considered Data Fiduciaries and are required to obtain the consent of individuals before processing personal data, except for certain permissible purposes listed below Section 7. 

A significant financial penalty is also introduced in the legislation, with data protection violations resulting in fines as high as Rs 250 crore. On November 13, 2025, MeitY notified the DPDP Rules for setting up the operational framework, with phased implementation over a period of 18 months. However, news publishers contend that the legislation does not specifically exempt journalistic activities from its provisions. 

A clear provision for news reporting is not provided by Section 7, which identifies legitimate purposes for processing personal information, nor by Section 17, which lists exemptions from the Act. According to the DNPA, this omission may pose significant challenges for reporters investigating individuals, institutions, or organizations. 

While investigating issues involving public accountability, journalists often obtain personal information from public records, interviews, documents, and other sources. A lack of a journalistic exemption may raise questions about whether consent is required before such information may be collected or used. Further, the association emphasized that earlier versions of data protection legislation, drafted in 2018, 2019, and 2021, included exemptions for journalistic purposes. They have been removed from the final framework and are a key part of the legal challenge. 

Moreover, the dispute also involves amendments to the Right to Information Act (RTI Act), which raise concerns regarding the impact of the new provisions on transparency and access to government information. DPDP Rule 23 also presents a challenge, which provides the Central Government with the authority to request information from Data Fiduciaries and intermediaries through an authorized agent. Moreover, the rule prohibits these entities from disclosing the fact that a request has been made.

News publishers have expressed concern over the possibility that the provision could affect the confidentiality of journalistic sources and create confusion regarding the handling of information obtained during investigations. Moreover, the association has questioned the amendment to Section 8(1)(j) of the Right to Information Act, which was implemented by Section 44(3) of the DPDP Act. 

A public authority previously had the option of withholding personal information that had no connection to public activities or that could cause an unwarranted invasion of privacy. If a larger public interest justified the disclosure, information could be released. Information related to personal information has been broadly exempted from the amended provision. 

Publishers argue that this change could make it more difficult for them to obtain government records required for investigations of matters such as conflicts of interest, public appointments and the use of public funds. Those seeking information about welfare programs, recruitment processes, and government services can also benefit from such information. However, the amendment does not remove every route for disclosure. 

Information may be released in accordance with Section 8(2) of the RTI Act when the public interest outweighs the potential harm to protected interests. Despite the government's assertion that stronger privacy safeguards are necessary for preventing misuse of personal information, the current provision pertaining to public interest continues to protect transparency as it does today. In addition, the legal dispute involves constitutional protections of privacy.

In its 2017 Justice K.S. Puttaswamy decision, the Supreme Court recognized privacy as a fundamental right under Article 21, albeit clarifying that the right is not absolute. This case raises the question as to how that protection should be applied simultaneously with freedom of speech and information access rights for the public. After issuing notice to the Centre, the Supreme Court declined to grant an interim stay on the challenged provisions before hearing the government's response. 

According to the bench, a blanket restriction on disclosure of digital personal information is not necessary, but a more proportionate approach is required. Additional hearings will be held on November 17, 2026 in regards to this matter. An examination by the court may have broader implications for how the privacy laws in India apply to news organizations, investigative reporting, and the public's right of access to public records.

It is expected that the Supreme Court's decision in this case will have a significant impact on the balance between individuals' rights to privacy, freedom of the press, and access to information for the general public. Its findings may also affect the way news organizations handle personal data when conducting investigations in India.

SonicWall Patches Exploited VPN Authentication Flaw

 

SonicWall has released security updates addressing a high severity vulnerability in SonicOS that could allow attackers to bypass SAML authentication and its associated multifactor authentication requirements. Tracked as CVE-2026-19868, the flaw affects the SSL VPN component of the operating system used by SonicWall firewalls. The company disclosed the issue alongside six other vulnerabilities in an advisory published on November 6, 2026. Its security team investigated a report indicating potential exploitation, raising concerns for organizations relying on affected appliances to secure remote connections. 

The vulnerability does not allow anyone to enter without credentials. Instead, an attacker must possess valid credentials for an alternative authentication method. Those credentials could then be used to bypass SAML authentication controls, potentially avoiding multifactor authentication enforced through SAML. According to SonicWall, exposure exists only when SAML login is enabled for the SSL VPN. The flaw received a CVSS severity score of 7.1 and was reported by Ryan Harris of The Electronic Office, distinguishing it from an unrestricted authentication bypass affecting every configuration. 

Affected products include Gen7 TZ, NSa, NSsp, and NSv firewalls running SonicOS 7.3.3-7015 or earlier. Gen8 TZ, NSa, and NSv firewalls running SonicOS 8.2.2-8015 or earlier are also vulnerable. SonicWall addressed the issue in SonicOS versions 7.3.4-7013 and 8.2.3-8015, respectively. The company said no workarounds are available and strongly urged customers to upgrade promptly. For administrators, the immediate priority is therefore identifying affected firewall models, checking their installed software versions, and applying the appropriate fixed release rather than relying on an unverified temporary configuration change. 

The United States Cybersecurity and Infrastructure Security Agency added the vulnerability to its Known Exploited Vulnerabilities catalog on November 6. Under Binding Operational Directive 26-04, federal agencies must address it by November 20. However, public information about exploitation remains limited. Neither SonicWall nor CISA disclosed details about the suspected attacks, their targets, or their impact. It also remains unclear whether attackers exploited the weakness before a patch became available. That distinction matters because the available reporting does not establish that this was a zero-day. 

The remaining six vulnerabilities broaden the advisory’s significance, although SonicWall did not identify them as exploited. Two management interface flaws, each rated 8.8, could permit unauthorized actions under certain circumstances without authentication. Three pre-authentication buffer overflows affect the SSL VPN service and TACACS+ authentication client, potentially causing application denial of service. A weak password hashing issue affects virtual appliances but requires highly privileged local access. Together, these findings make the updates relevant beyond the SAML bypass alone, while keeping each vulnerability’s prerequisites and consequences distinct.

AI in Policing Risks Amplifying Racial Bias, Researchers Warn

 




When the Los Angeles Police Department started feeding decades of arrest records into predictive algorithms, it believed it was upgrading how it approached crime. What it actually did, researchers now argue, was automate its existing prejudices.

The growing use of artificial intelligence in law enforcement is raising alarms among criminologists and legal scholars who say these systems absorb the biases already embedded in historical police data and repeat them at scale. Far from offering a neutral, data-driven view of crime, the tools risk entrenching the same inequalities they claim to transcend.

At the core of the problem is how these systems learn. AI tools for predictive policing are trained on past arrest and crime records, which means they begin with a picture of crime shaped by previous policing decisions rather than by crime itself. Areas that received heavier patrol in earlier decades show more recorded incidents. The algorithm reads that density as a future risk signal and directs officers back to those same neighborhoods. More arrests follow. The data is updated. The cycle repeats.

Sarah Brayne, a sociologist at the University of Texas at Austin, spent time inside the LAPD studying how the department used big data systems. In research published in the *American Sociological Review*, she found the department was increasingly using data to predict crime rather than respond to it. The data flowing into those systems was skewed from the start: crimes in public places were more likely to be recorded, and patrol resources were disproportionately concentrated in Black neighborhoods. Once that history was absorbed by the algorithm, Brayne wrote, "the predictions appear impartial." They were not. The models, she concluded, create "a feedback loop in which they not only predict events such as crime or police contact, but also contribute to their future occurrence."

The problem sharpens when that underlying data was produced under conditions of institutional misconduct. Researchers at New York University's AI Now Institute studied 13 jurisdictions across the US and found that in nine of them, police departments had trained predictive systems on records gathered during documented periods of unlawful or biased policing. Chicago is the starkest case. The city's police department was under federal investigation for discriminatory practices at the same moment it adopted a risk-flagging algorithm to identify people likely to be involved in shootings. The residents federal investigators had identified as targets of biased policing overlapped substantially with those the algorithm flagged. The list eventually grew to more than 400,000 names, 56 percent of them Black men.

Chicago shut down the program in 2019 after its own inspector general raised concerns about its effectiveness. Los Angeles scrapped a similar initiative, Operation LASER, the same year. A 2023 analysis of Geolitica, formerly known as PredPol, one of the most widely deployed predictive policing tools in the country, found a success rate below half a percent across more than 23,000 predictions made in Plainfield, New Jersey.

Not everyone in the field believes the technology is fundamentally broken. Dr. Dimitrios Kollias, an associate professor in multimodal artificial intelligence at Queen Mary University of London, argues that modern AI systems do not simply replay their training data. "They can combine learned information in new ways and generate outputs that were not explicitly present in those examples," he told the BBC. He acknowledges dirty data is a genuine concern but argues systems can be tested for unfair outcomes and redesigned when they fail. As those systems grow more autonomous, he adds, ensuring they remain under meaningful human control becomes a priority in its own right.

The consequences of algorithmic bias run well beyond law enforcement. A 2019 study published in the journal Science examined a healthcare AI tool used to allocate additional patient support across US hospitals. The system measured patient need by predicting the cost of their care. Because less was already being spent on Black patients than on equally sick white patients, often due to poorer access to care, the algorithm systematically directed resources toward white patients. When researchers recalibrated it to predict illness directly rather than cost, the share of Black patients selected for extra support would have risen from roughly 18 percent to 47 percent. The fix was straightforward once someone looked for the problem. That is precisely the case researchers make for independent oversight.

Legislators are beginning to respond. In January 2024, seven US Congress members asked the Justice Department to pause grant funding for predictive policing programs until their discriminatory impact could be assessed. A White House policy from March 2024 requires federal agencies to independently test rights-impacting AI tools, though the mandate does not extend to state and local police departments. In Britain, 17 civil society organizations called the same year for a full ban on predictive policing.

Dr. Carolyn McKay, an associate professor in digital justice at the University of Sydney Law School, says cleaning up biased data is not a matter of removing a few stray errors. The corrupted records are not sitting at the edges of an otherwise sound dataset. They run through the foundation the algorithm was built on. Even systems redesigned to flag locations rather than individual people can produce the same outcomes, she warns, because the neighborhoods they target were shaped by years of concentrated policing long before any algorithm got involved.

The root of the problem, most researchers agree, is not the machine. It is the human judgment baked into the data the machine inherited. The algorithm did not decide what suspicious behavior looked like, or which crimes were worth recording. People did. Until those decisions are independently examined, AI will keep reflecting them back.



Barracuda Patches Two Security Flaws That Could Let Attackers Take Over Email Security Gateways


Experts have shown how two vulnerabilities in Barracuda's Email Security Gateway can be chained to execute arbitrary commands with root privileges without requiring an attacker to log in.

The vulnerabilities, tracked as CVE-2026-116606 and CVE-2026-111560, affect Barracuda's email-filtering appliance and could allow remote attackers to bypass security restrictions and gain complete control of vulnerable systems.

According to cybersecurity firm watchTowr, which published its technical analysis, the attack chain combines an authorization bypass flaw with a command injection vulnerability. Barracuda released security patches for the issues earlier this week.

The first vulnerability, CVE-2026-116606, is an authorization bypass flaw that allows unauthenticated attackers to access a configuration restoration function and modify the appliance's global settings. The second, CVE-2026-111560, is a command injection vulnerability that enables commands to execute with root privileges.

Mandiant assigned CVSS severity scores of 9.3 and 8.6 to the two vulnerabilities, respectively.

How the attack chain works

In its technical investigation, watchTowr discovered that the authorization bypass stems from the appliance's password-change process. When a password change request fails, the system incorrectly returns a low-privilege user role instead of terminating the request completely.

The researchers also found that Barracuda's backup verification mechanism relies on a secret embedded within the appliance's code. Since this secret is not securely protected, attackers can generate a valid checksum for a specially crafted configuration backup and restore it on the targeted device.

The uploaded configuration can contain a manipulated timezone value. When the appliance processes this setting, it passes the value to a shell command that executes with root privileges.

watchTowr demonstrated the attack by successfully writing a file to the appliance with root-level permissions.

Affected products

CVE-2026-116606 affects Barracuda Email Security Gateway, while CVE-2026-111560 impacts five additional products, including Load Balancer Application Delivery Controller (ADC), Message Archiver, WAF Control Center, Web Application Firewall (WAF), and Web Security Gateway (WSG).

However, the complete unauthenticated attack chain applies specifically to Email Security Gateway. Exploitation of the command injection vulnerability on the other affected products requires administrator access.

What next?

Barracuda has released security updates addressing both vulnerabilities and recommends that customers install the appropriate patches or upgrade to the latest fixed firmware versions.

As of the disclosure, neither vulnerability had been listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no publicly reported incidents linked the flaws to active exploitation.

Data Sovereignty Is Essential for India's Digital Infrastructure, Says RBI Governor


Sanjay Malhotra, Governor of the Reserve Bank of India (RBI), emphasized the significance of maintaining sovereign data centers in order to safeguard critical financial information and strengthen the country's digital infrastructure. As information technology has become an integral part of the banking industry, security infrastructure, operational resilience, and cybersecurity have become increasingly important in maintaining financial stability, especially in light of the growing threat landscape being shaped by artificial intelligence (AI). 


Prime Minister Narendra Modi inaugurated the RBI's new data center complex and Cybersecurity Training Institute in Bhubaneswar on October 25, and made these remarks following the inauguration. With a capital investment of Rs 169 crore, the facility is expected to enhance the reliability of critical financial services and to reduce the likelihood that essential banking operations will be disrupted.

A spokesperson for Doordarshan reported that Malhotra explained that the central bank's technology infrastructure facilitates the use of applications by the general public, financial institutions, and government departments. He pointed out that information technology cannot be considered merely a supporting function, as several essential financial operations are directly dependent upon the availability and security of these technologies. 

NEFT and RTGS are major payment infrastructures that will be supported by the new data center. Furthermore, the RBI's integrated ombudsman system and applications used by financial institutions regulated by the central bank will be supported by the new data center. In addition to government banking operations, it will also accommodate financial institutions regulated by the RBI. 

A key component of Malhotra's statement was the RBI's role in the Unified Payments Interface (UPI) ecosystem in India. Although UPI is operated by the National Payments Corporation of India (NPCI), final settlement of transactions takes place through the RBI's data centres and applications. To ensure the availability of the central bank's infrastructure within the wider digital payments ecosystem, it is important. 

Four independent data centres are located within the Bhubaneswar complex, which has been accredited as Tier IV by the Uptime Institute, the highest level of its data centre classification. This facility will be operated independently of third party cloud service providers, allowing RBI to maintain greater control over its critical infrastructure and sensitive financial information. Additionally, the project's geographical location will contribute to its resilience. 

A geographically separated and seismically isolated location in Bhubaneswar reduces the possibility that a localised disruption will affect all facilities simultaneously. The RBI previously operated three data centers in Maharashtra. Additionally, this development reflects the increasing importance of data sovereignty in the Indian financial infrastructure, where uninterrupted access to critical systems and the control of sensitive information remain essential security priorities. 

As part of the RBI's infrastructure security efforts, cybersecurity expertise is also being developed throughout the financial sector. In the Bhubaneswar project, there will be a Cybersecurity Training Institute, which will occupie approximately two-thirds of the campus, and the remaining portion will accommodate the data centre. It is intended that the institute will provide training to personnel of the RBI, bank employees, and professionals from other financial institutions. 

A number of emerging technologies, such as artificial intelligence (AI), big data analytics, quantum technology, and blockchain, will be studied as part of its programming. There will also be research activities conducted in order to investigate ways to improve the security and efficiency of financial systems. With AI posing new challenges to financial institutions, specialized training is becoming increasingly important.

The technology can provide opportunities for improving banking operations and security monitoring; however, if it is misused, it can result in cyberattacks, automated fraud, and attempts to exploit weaknesses in digital systems, increasing in sophistication. Financial sector readiness therefore relies heavily on cybersecurity professionals staying up to date on these developments. 

Governor of the Reserve Bank, Sanjay Malhotra, stressed the need to maintain personnel informed of technological developments and the growing importance of cybersecurity in the context of artificial intelligence. By attending the institute, financial sector professionals will be better equipped to comprehend emerging risks and respond to changes in cybersecurity. In addition to investing in digital infrastructure, the initiative emphasizes the importance of building human expertise. 

For data centers and advanced technology systems to be secure, trained professionals must manage operations, identify security weaknesses, and ensure service reliability are required. It was pointed out during the inauguration that cybersecurity was directly related to India's economic security by Prime Minister Narendra Modi. As financial services become increasingly dependent on digital technologies and digital banking, it becomes increasingly important to protect the financial infrastructure.

As well as highlighting the institute's role in developing cybersecurity and emerging technologies, Finance Minister Nirmala Sitharaman also highlighted the institute's efforts. Due to its emphasis on energy efficiency and water conservation, the RBI has also applied for a Platinum rating with the Indian Green Building Council. 

Bhubaneswar represents a larger effort to strengthen India's control over critical financial technology infrastructure by incorporating locally sourced materials in its construction approach. To protect the country's financial ecosystem, sovereign data management, geographically distributed infrastructure, and specialized cybersecurity training will remain important. As digital payments and artificial intelligence-driven services continue to increase, a comprehensive data management system, geographically distributed infrastructure, and cybersecurity training will be essential. 

An important strategic investment is being made in Indian financial infrastructure with the establishment of the sovereign data centre and cybersecurity training institute. In order to enhance the long-term reliability and resilience of the country's digital financial systems, the RBI intends to strengthen control over critical financial data and develop specialised cybersecurity expertise.

Bogotá Investigates Possible Health Agency Email Compromise Linked to European Airport Bomb Hoax

 

Authorities in Bogota, Colombia, have opened an investigation into whether an email account used by a public health agency was accessed without authorisation or if it was spoofed in a bomb threat email sent to an airport in Europe. The threat comes after a wave of bomb threats via email has caused chaos at airports throughout Europe since Monday. Flights have been diverted, and security checks and searches have been conducted but so far no devices have been found. 

In the Bogota related email seen by Recorded Future News, the message was sent to contacts in Rome’s Fiumicino Airport and appeared to be sent using the Subred Sur Occidente domain. This is a public hospital network covering the southern west of Bogota. The email said there were explosives on board two flights heading to Rome. One was a Finnair flight from Helsinki which was escorted into Rome by Italian Air Force fighter jets. The other was an Aer Lingus flight which was diverted to a French military base. 

Bogota’s mayor’s office has confirmed it received an international alert regarding a possible use of an email address used by a health agency in the city. An investigation has been ordered to find out what happened, according to a statement on the Subred Sur Occidente website. The administration also highlighted that there have been suspected cyber-attacks on public institutions recently. It cannot be ruled out that international hackers have been involved or that government email addresses have been compromised. 

It is still being investigated whether the email account used by the hospital network was used to send the threat, or if it was just spoofed. There is also no evidence to currently link staff from the health agency to the threat or why the domain was chosen. Several of the threats to European airports have been signed off with names linked to a Russian misogynistic group which is banned in Russia. 

However experts have warned that this does not mean they can be blamed. The threats have also been sent to several Irish media outlets on Friday. The messages claimed to be linked to the same group. The Irish government have said the threats to media outlets are serious and it is not clear if they have come from individuals or an organised effort. 

However the timing and similarities to the airport disruptions mean it is likely to be an organised campaign. A spokesperson for the Taoiseach of Ireland could not be immediately reached to ask if the government’s statement was based on any specific intelligence. It is not known who has sent the series of threats.

FCC Starts Blocking Devices for What's Inside Them, Then Gives Intel a Pass

 



The Federal Communications Commission moved this month to block two consumer gadgets from the American market, not because of who made them, but because of a chip buried inside. A dashcam and a wireless video transmitter both contained components manufactured by HiSilicon, a Huawei subsidiary, putting them on the wrong side of a rule that took effect October 13 and extends Washington's existing tech blacklist deep into the supply chain.

The same day those products were pulled, October 22, the FCC handed Intel a one-year reprieve for the foreign-built robots running in its semiconductor factories. The two decisions landed together, and together they sketch the shape of a problem that will follow this policy for years.


What Changed and Why It Matters

The FCC has maintained what it calls the Covered List since 2021, a register of foreign technology companies whose products are deemed national security risks. Placement on the list means a company's equipment cannot receive radiofrequency authorization in the United States, which amounts to a ban on importing and selling it here. For years, the restriction was straightforward: it applied to products built by listed companies. Huawei was on the list; Huawei routers were blocked.

The new Third Report and Order changed the terms. It bars RF authorization for any device that incorporates logic-bearing components from a Covered List entity, so long as the end product itself would have been blocked. The two gadgets flagged on October 22 were the first to be caught under this framework, but they will not be the last.

The FCC's characterization of the HiSilicon chips is worth noting. The agency called them "foreign surveillance chips" and cited their "built-in detection algorithms for human faces," a feature sold to consumers as a way to identify strangers near a home. HiSilicon is a Huawei subsidiary, and Huawei is already on the Covered List, which is what triggered the rule. FCC Chairman Brendan Carr praised the enforcement action and said more would follow.

"Manufacturers must now conduct their own supply chain audits to determine whether any of their parts trigger the rule, with limited guidance on where to look."


A Rule With Gaps

The logic is clean on paper. If a company is considered a threat, its chips should not enter American products regardless of who assembles them. But applying that logic requires knowing what is inside a device, and that is harder than it sounds.

No authoritative list currently exists identifying which companies manufacture covered components. Huawei itself did not name HiSilicon in a 2023 subsidiary disclosure filing to the FCC. That gap means the burden of compliance falls on manufacturers who must audit their own supply chains, often without clear guidance on which subsidiaries or affiliates to look for. A separate FCC proceeding that would require Covered List entities to submit complete subsidiary and affiliate disclosures is still pending and not yet in effect.

The rule's reach also has limits. It applies only to components made by entities actually named on the Covered List. Unnamed manufacturers of foreign industrial robots or consumer routers, for instance, do not fall under it, even if those products are covered under the separate "sector-based" rules the FCC introduced for certain product categories starting in December 2025.


Intel's Narrow Escape, and Its Clock Problem

When the FCC added humanoid robots, quadrupeds, and other industrial robotic devices to the Covered List in July 2026, it created an immediate operational problem for Intel. The company's semiconductor fabrication plants run on automated guided vehicles, or AGVs, purpose-built machines that shuttle materials across factory floors. Intel says these machines have been in continuous operation for roughly two decades and that no American-made alternatives meet its technical requirements.

Intel applied for relief before it was clear the rule even applied to its machines, flagging the uncertainty in its filing. The FCC granted a one-year hardware waiver on October 22, the first of its kind in the robotics category. Intel committed to keeping the vehicles on-site under its control, making no changes that would improve their RF characteristics, and not introducing new capabilities.

The problem is the timeline. The hardware waiver expires in October 2027. A separate waiver covering software and firmware updates on the same machines runs through January 2029, leaving a 15-month gap between the two deadlines. Replacing industrial robots typically requires years of commissioning, procurement evaluation, and integration work, a timeline that does not fit inside 12 months. At least one industry analyst has described the arrangement as "a temporary fix for a long-term problem." Intel will need to identify domestic alternatives, pursue an extension, or seek a longer-term exemption well before next fall's deadline.


What Comes Next

The FCC's Covered List has been moving in one direction: more products, more companies, more components. Drones, consumer-grade routers, power inverters, and now industrial robots have all been added to sector-based restrictions that cover foreign-produced products across entire categories, regardless of which specific company made them. Companies operating in those sectors can apply to the Department of Homeland Security or the Department of War for conditional approval, which requires committing to a domestic manufacturing onshoring plan.

The two decisions on October 22 sit on opposite ends of that spectrum. The HiSilicon enforcement shows the new component rule starting to bite, pulling products off the market that passed previous scrutiny because the finished gadget was not made by a listed company. The Intel waiver shows how far the domestic alternative market still has to go before the restrictions can hold without exceptions. The list is getting sharper. The supply chain it assumes into existence is still being assembled.



Hackers Exploit OpenSSH SSHole Flaw Within Hours

 

A newly disclosed OpenSSH vulnerability, nicknamed SSHole, is already being exploited in the wild. The flaw, tracked as CVE-2026-123158 and carrying a CVSS score of 8.1, lets unauthenticated attackers log in to certain Linux accounts that have no usable password set. Security firm Previdian observed the first exploitation attempt less than nine hours after the vulnerability was published, and confirmed successful root access on an Alpine Linux honeypot. 

The issue affects Linux systems running OpenSSH on the musl C library with Pluggable Authentication Modules (PAM) disabled. Alpine Linux’s default OpenSSH server configuration is among the affected setups. An attacker can send an oversized password—between 257 and 1,024 bytes—to trigger the bug and gain access to accounts configured with an asterisk (*) as their password hash. This means attackers do not need to steal SSH keys or valid credentials to obtain access. 

SSHole stems from password-handling behavior linked to a 2016 patch for CVE-2016-6210, a username-enumeration flaw. Under the specific conditions, OpenSSH mistakenly treats a failed password-hashing operation as successful authentication because it produces the same asterisk value used to mark password-disabled accounts. The SSH daemon then compares that value with the account’s stored password field and allows the login. Importantly, the flaw does not bypass passwords on accounts that have valid password hashes. 

The consequences depend heavily on the privileges of the compromised account. A successful attack grants the attacker the permissions already held by that account, which could include access to deployment credentials, application secrets, and connected infrastructure. From there, intruders may move laterally across systems or disrupt services. The vulnerability does not affect Dropbear, glibc-based Linux distributions, non-Linux systems, or systems that authenticate passwords through PAM.

Administrators should act quickly by installing OpenSSH 10.6p2 or their distribution’s patched package and restarting the sshd service. Alpine also advises reviewing /var/log/messages for “Accepted password for” entries involving accounts that should not accept password logins, including root, Alpine, or key-only users. Administrators should inspect recent users, files, authorized keys, and doas usage; if a suspicious login cannot be ruled out, the system should be treated as compromised.

AI-Powered CEO Impersonation Scheme Allegedly Defrauded Companies of $129 Million

 

Three men have been indicted in the United States for an alleged international fraud scheme in which they used artificial intelligence to impersonate corporate executives and legal professionals to trick employees into sending around $129 million to their accounts. 

Jacob Soall, Sharon Hazan and Guy Sheetrit have been charged with pretending to be company CEOs and lawyers to convince employees that large transactions were needed. Between 2024 and 2026, the trio allegedly conspired to use AI to create fake audio and video of real people, according to the U.S. Department of Justice. They used AI to make their impersonations realistic enough to fool corporate workers. 

The trio now face numerous charges including wire fraud, money laundering and aggravated identity theft. If they are found guilty, they could face a maximum sentence of 104 years in prison. They called employees and pretended to be their company’s chief executive, with the alleged fraudsters claiming they needed urgent financial transactions to be completed and that it was confidential. They would then tell employees to contact lawyers on behalf of the company. 

AI was used to create copies of the lawyers’ voices and appearances. Soall was reported to have taken on the role of impersonating lawyers and had scripts ready to mimic how they would speak. Once they had convinced employees to approve the transactions, the money was sent through bank accounts in the United States, Europe, the United Arab Emirates and China. 

The cash was then transferred into cryptocurrency. Several organisations were allegedly scammed including a hospital in Missouri who lost almost $5 million, a bank in Rhode Island who lost $2.6 million and a hospital in California who lost $2.9 million. Other alleged victims included a technology company in the UK who lost $11.5 million, a financial company in Massachusetts who lost $4.6 million and a pet food company in Florida who lost $5.2 million. Hazan is alleged to have managed the money laundering. 

In court documents, Hazan claimed he had laundered $400 million since 1994. He was previously convicted of bank fraud in 2008. All three suspects are currently in custody. Soall and Hazan were arrested in Spain during the summer whilst Sheetrit was detained in the United Kingdom in September. The Justice Department said they are all facing extradition requests. 

The FBI has warned criminals are increasingly using new technology to commit complex financial frauds. James Barnacle, a senior FBI official, said the alleged fraud is an example of how sophisticated technology can be used to commit large-scale crime. The bureau has encouraged businesses who may have been targeted to report any suspected incidents.

Hackers Exploit Malicious CWP Web Server to Backdoor Linux Systems


Linux backdoors have been discovered that have been maliciously implanted into servers that are running Control Web Panel (CWP) via trojanized versions of its web server component, raising concerns about the security of hosting infrastructure in general. By crafted HTTP requests, attackers are able to execute commands remotely while concealing their activity from normal server access logs, a technique known as CWPdoor. 

The malware was discovered by security researchers at XLab, the research division of QiAnXin Technology Group, on June 29 after capturing a malicious shell script. Scripted updates disguised themselves as legitimate software updates, replacing the original cwpsrv binary with a modified version that included a backdoor. Versions of Web Servers 1.15.10 and 1.24.0 were affected. 

The CentOS Web Panel was previously known as the CentOS Web Panel, which is a free open-source web hosting management system for managing Linux servers and services, including email, DNS and databases. A web server component, known as CWPsrv, is responsible for handling requests to the management interface, making this compromise of particular concern to server administrators. During the month preceding the investigation, more than 340,000 CWP instances were exposed on the internet, according to XLab. 

Even though public exposure does not guarantee infection, the number of attacks targeting this software indicates the potential reach of such attacks. 

Malicious Update Script Conceals the Infection

CWPdoor infections begin with scripts modifying the legitimate CCWPSRV executable with a trojanized version. In addition to installing the malicious binary, the script performs several other actions intended to make detection difficult. As a result, files and directories affected by the virus are restored to their original timestamps, temporary installation files are removed, and command history records are cleared.

Through these methods, the replacement is less visible and routine administrative checks are less effective. The malware does not behave like a conventional backdoor that continually listens for incoming connections, but instead remains dormant until its operators issue a specially constructed HTTP request that triggers its operation. Consequently, ordinary network monitoring is unable to detect the threat due to its passive execution method. 

The compromised web server continues to perform its legitimate functions while maintaining the ability to execute attacker-controlled commands when a valid request arrives. In particular, XLab described the malware as exceptionally stealthy, owing to its request validation mechanism and ability to interfere with server logging. By using these capabilities, a backdoor can be concealed within a trusted component of the server rather than appearing as a standalone process that appears to be suspicious. 

Encrypted Requests and Log Manipulation Hide Attacker Activity 

A malicious HTTP request carries three custom headers that are used by CWPdoor to control the execution of attacker commands. CWPdoor utilizes encryption and digital signature verification to ensure that attacker commands are executed in a controlled manner. X-Ngx-Integrity-Data contains an encrypted command; X-Ngx-Integrity-Time specifies a timestamp; and X-Ngx-Integrity-Sig contains an RSA signature. 

The backdoor validates the RSA signature before executing a command. The malware decrypts the command once it has passed these checks and forwards it to the helper process for execution. Both commands and their output are protected using AES-256-CBC encryption. With the signature mechanism, attackers or external parties are also prevented from altering the encrypted payload or timestamp without invalidating the request. 

As a result, the backdoor can only be activated when the request has been correctly signed, providing replay protection. CWPdoor has also been shown to suppress evidence of malicious activity in a significant way. It interferes with the logging module of the web server, preventing regular access log entries from displaying requests that trigger the backdoor. During routine security investigations, this can lead to administrators lacking crucial evidence. 

VirusTotal Sample Points to Active Infections

The analysis indicated that the CWPdoor sample had been uploaded to VirusTotal on September 30, along with the Ebury backdoor. Researchers discovered that the trojanized cwpsrv binary did not receive a single antivirus detection out of 63 security products tested. The discovery indicates that the malware has reached beyond testing and is already present on compromised systems. 

It is unclear, however, whether CWPdoor and Ebury are operated by the same threat actors or whether they were installed independently on the same server. Ebury is an extensive Linux malware operation known for its backdoors and credential stealing capabilities. Since the malware was first identified in 2009, ESET reported that nearly 400,000 servers were compromised. 

XLab Shares Detection and Mitigation Measures

This malware has been identified by XLab. It is recommended that administrators inspect CWP servers for specific indicators associated with it. These include the ngx_http_integrity_helper Unix socket, unexpected helper processes launched by cwpsrv, and strings containing X-Ngx-Integrity. It is also recommended to check the integrity of the cwpsrv executable rather than relying on file timestamps, because the malicious installer may restore the values of the file timestamps to conceal unauthorized modifications, according to researchers. 

A legitimate copy of the web server binary should be restored by administrators, the CWP must be updated to the newest version, and all control panel credentials must be rotated. Furthermore, the affected host should be subjected to an extensive security investigation to determine whether it has been infected with malware or unauthorized access.

Because CWPdoor is capable of executing attacker-supplied commands, replacing the compromised binary may not be sufficient to secure the system. Server credentials, including privileged access accounts, should be treated as potentially vulnerable.

DigiCert Hack Exposes Customer Details, Passports, and Driver's Licences


DigiCert has disclosed a data breach after a server migration error exposed an internal business system to the internet, allowing unauthorized users to access archived customer information and sensitive identity documents.

The exposed information included customers' names, business email addresses, phone numbers and business addresses. In some cases, the records also contained personal identification documents, including driver's licences, passports and utility bills.

DigiCert has started notifying affected customers about the incident. The company is also reviewing archived identification documents to identify the individuals whose personal documents may have been accessed.

Server migration error led to unauthorized access

According to an incident report published on Mozilla's Bugzilla platform, the security issue originated in February 2025, when DigiCert migrated an internal business system to a different availability zone. The migration inadvertently made the system accessible from the public internet, although it was previously restricted to users connected through a virtual private network (VPN).

The exposed system contained a self-registration feature designed for other applications. This feature allowed external users to create accounts without requiring the usual internal authorization.

Although these newly created accounts were not assigned to any particular application, an authorization vulnerability allowed them to access archived customer information in read-only mode.

DigiCert discovered unauthorized accounts on the exposed system in June 2026. However, the company initially believed that these accounts could not access customer records because they had not been assigned to an application.

The company received a report through its managed security research program highlighting the possibility of external users creating accounts on the system.

DigiCert implemented security measures to restrict access and address the authorization issue. However, it did not immediately recognize that customer information had already been accessed.

An investigation confirmed that an unauthorized account had accessed archived customer records between June 27 and July 2, 2026. DigiCert confirmed the data breach on October 19, 2026.

The company acknowledged that the incident was initially treated as an account-creation issue rather than a potential data-access incident.

Customer information and identity documents exposed

The compromised records primarily contained business contact information shared with DigiCert during customer verification and other business processes.

However, some archived records also included sensitive identification documents submitted by customers. These documents could include government-issued identification, such as passports and driver's licences, as well as utility bills containing personal information.

DigiCert stated that the unauthorized account had read-only access and could not modify customer records, approve certificate validations or issue digital certificates.

Robust security measures by DigiCert

After the investigation, DigiCert disabled the self-registration feature, restricted access to the affected system and introduced additional access controls to prevent unauthorized users from accessing archived information.

The company also confirmed that its core certificate authority services, including CertCentral and DigiCert ONE, were not compromised. Customer login credentials and previously issued digital certificates also remain secure.

India’s Road Ministry Orders Forensic Audit of Four Transport Portals After Vehicle Data Found for Sale on Telegram

 




The Ministry of Road Transport and Highways has directed India's national cybersecurity agency to conduct a forensic security audit of four of its core digital portals, following reports that personal data of vehicle owners was being sold through Telegram bots and mobile applications for as little as ₹5 per lookup.

The ministry ordered the Computer Emergency Response Team of India, commonly known as CERT-In, to audit VAHAN, SARATHI, e-Challan, and the Pollution Under Control Certificate portal. These four platforms collectively hold some of the most sensitive civic data in the country, covering vehicle registrations, driving licences, traffic challans, and vehicle fitness records for hundreds of millions of Indians.

The trigger for the audit was a report documenting an active Telegram-based service that allowed anyone to query a vehicle registration number and receive the owner's full name, father's name, present and permanent addresses, PIN code, and mobile number. The same service also offered driving licence details, challan history, FASTag information, and downloadable copies of registration certificates and driving licences. A cybersecurity firm, Cyderes, traced the service's backup channel to 21,329 subscribers before it was taken down. It rebuilt itself under new handles within weeks.

The scale of commercial access to these government databases is not incidental. As of the latest available figures, 25,314 private corporate entities held active credentials for the four portals, collectively running 1.708 crore searches over a 33-month period. Officials are now reviewing whether daily search limits and usage guidelines were actually enforced during this period or simply existed on paper.

The concern does not stop at the portals themselves. On the Unified Logistics Interface Platform, managed by the National Industrial Corridor Development Corporation, some authorized entities reportedly logged more than five million data transactions in a single month. The National Informatics Centre has been directed to audit these access patterns. Under revised protocols, any government body seeking data through this logistics platform will now require explicit authorization from the Transport Secretary, with requesting officers verified through Aadhaar-based digital signature certificates or video-based KYC procedures.

The ministry has also written to app store operators, including Google, requesting the removal of applications that surface vehicle owner details without adequate safeguards. Two apps drew particular attention: Vehicle Information App, with roughly 10 million downloads, and VehicleSetu, with about 1 million. The largest vehicle information app on the Play Store reportedly carries over 100 million downloads. MoRTH is also reviewing its data-sharing arrangements with the Ministry of Electronics and Information Technology in light of the Digital Personal Data Protection Act, 2023.

What makes this episode harder to dismiss as a simple breach is that no government database was hacked in the traditional sense. Investigators found no sign of a backend intrusion. Instead, Cyderes traced the data flow to credentials held by licensed identity verification companies, with lookups routed through authentication tokens on a third-party platform. As recently as August 4, 2026, one such route was still returning full VAHAN records including mobile numbers. This points less to a technical failure and more to systemic gaps in how credential use is monitored and how downstream sharing by licensed entities is controlled.

The government's relationship with vehicle data predates this episode by several years. In 2019, Transport Minister Nitin Gadkari told the Rajya Sabha that the government had earned ₹65 crore from selling VAHAN and SARATHI data to 87 private companies and 32 government bodies under a bulk data sharing policy. By February 2021, that revenue figure had grown to over ₹111 crore, with more than 170 recipient entities. Recipients included automakers, insurance firms, and second-hand vehicle dealers. The Internet Freedom Foundation noted at the time, and has reiterated since, that the Motor Vehicles Act contains no provision authorising the commercial transfer of this data to private companies.

IFF sent a formal representation to MoRTH, the NIC, and CERT-In on September 23, 2026, asking for the incident to be registered as a cyber incident, for server logs to be preserved, and for a comprehensive forensic audit. It also asked the ministry to publish a register of all entities currently holding access credentials, introduce technical controls to cap and monitor search volumes, and notify affected individuals.

The ministry says "controlled private access will continue to support commercial efficiency," language that suggests the government is not planning to end third-party access to these databases altogether. What it has not yet addressed publicly is how it will verify that the access controls now being introduced will hold in practice, given that the previous framework apparently operated without meaningful enforcement for years.

India's Digital Personal Data Protection Act places compliance obligations on data fiduciaries starting May 2027, with penalties reaching ₹250 crore for violations. The forensic audit ordered by MoRTH will now determine whether the exposure was a question of technical vulnerability, policy failure, or both.



DreamHost Data Breach Exposes FTP Credentials and Webmail Session Information

 

DreamHost has disclosed a security breach in which an unauthorised party accessed its web-based File Manager and potentially obtained sensitive customer information, including FTP/SFTP credentials and webmail session details. The intrusion reportedly began in August 2026 and continued until October 23, when the hosting provider discovered the incident. 

The American web hosting company and domain registrar initially informed customers of a cybersecurity incident that required password resets for email and FTP/SFTP accounts. Its subsequent breach notification provided further details about the compromised system and the information that may have been exposed. 

According to DreamHost, the attacker exploited a vulnerability in the software running its File Manager service at files.dreamhost.com. Customers who logged into the platform during the exposure period may have had their FTP/SFTP usernames and passwords accessed. The company has not disclosed the precise number of affected accounts. The investigation also identified a possible exposure involving DreamHost’s webmail infrastructure. 

A limited number of users may have had session information accessed, potentially including credentials. The company described the incident as appearing deliberate and said its teams had been working continuously to contain the intrusion. DreamHost stated that it had found no evidence of unauthorised access to control panel login credentials or customer billing and payment information. Payment details are handled by an external provider, according to the company. 

Following discovery of the breach, DreamHost said it cut off the attacker’s access and fixed the vulnerability used to compromise the File Manager platform. It also terminated active sessions belonging to potentially affected users and invalidated passwords to reduce the possibility of continued unauthorised access. Customers who received breach notifications are being advised to inspect their website files for unexpected modifications and examine webmail settings for unfamiliar forwarding rules or filters. They should also update passwords on other services if the same credentials were reused elsewhere. 

To support affected customers, DreamHost is offering one year of credit monitoring and identity theft protection through Equifax. Recipients have also been encouraged to consider placing a fraud alert on their credit files or requesting a security freeze to help prevent fraudulent activity. BleepingComputer reported that it had contacted DreamHost multiple times seeking clarification about the breach, including the number of impacted accounts, but had not received a response at the time of publication.

Bank Phishing Sites Fake Suspensions to Evade Takedowns

 

Cybercriminals operating a large-scale bank-phishing campaign have adopted a sophisticated method to evade takedown efforts: presenting malicious websites as inactive to security teams while continuing to target new victims. According to cybersecurity firm Kela, the campaign’s phishing infrastructure records each visitor’s IP address. First-time visitors are directed to convincing counterfeit bank login pages, whereas returning visitors from the same IP address are shown a fabricated “account suspended” notice. This technique creates the impression that the domain has already been shut down, allowing the operation to remain active while undermining verification processes. 

The campaign has been active since May and employs more than 300 fraudulent domains. Of these, 248 impersonate 189 financial institutions in the United States, with most domains registered between July and September 2026. As of October 25, 183 of the targeted organizations still had live look-alike websites. The operation primarily focuses on mid-sized regional banks and appears designed to obtain business-banking and treasury credentials rather than personal account credentials. Kela also identified 49 newly registered domains during the final week of October, indicating that the network remains active and expanding. 

The fraudulent domains follow recognizable naming conventions intended to increase their apparent legitimacy. Many incorporate terms such as “secure,” “disable,” “protect,” “cancel,” “authorize,” “terminate,” “credentials,” or “commercial,” followed by the name of the targeted bank. A smaller but growing group uses domains resembling help desks, live-support portals, treasury portals, and “primary device” pages. Examples include look-alike domains associated with JPMorgan, Citi, BMO, and Santander. These naming patterns are designed to make the links appear urgent, official, and relevant to customers concerned about account security or payment issues. 

When a first-time visitor accesses one of these pages, the site displays the targeted bank’s branding and requests a user ID and password. Some pages also include a reCAPTCHA to reinforce the appearance of legitimacy. The browser tab is titled “Attention required,” imitating Cloudflare’s challenge page, while embedded scripts attempt to prevent users from accessing browser developer tools. Upon a subsequent visit from the same IP address, however, the page displays a fake hosting-provider suspension notice. This cloaking technique is specifically intended to disrupt the standard security workflow, in which analysts verify a reported site and then recheck it to confirm that it has been removed. 

The infrastructure is difficult to dismantle because it incorporates several defensive measures: easily repeatable domain-naming conventions, Cloudflare services that obscure the actual hosting location, IP-based cloaking, and shared servers capable of hosting new phishing domains after individual sites are removed. Kela also identified alternative evasion methods, including blank pages, blocking notices, and redirects to Google, which prevent public scanning services from fully documenting the campaign. Although the firm has not determined how victims are initially directed to the phishing pages, it found that the operation also targets victims in the United Kingdom, Australia, and New Zealand. Users are advised to avoid links in unsolicited communications and to access banking services directly through official applications or saved bookmarks.