Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Latest News

Cyberattack on Wellington IT Exposes Payee Information Across 40 Irish Credit Unions

  A cybersecurity incident involving Belfast-based technology provider Wellington IT has exposed sensitive financial information associated ...

All the recent news you need to know

Critical Cisco Expressway Vulnerability Exploited By Hackers Shortly After Public PoC Release

 

A Russian organisation was compromised via a vulnerability in Cisco Expressway. Shortly after public exploit code was published, attackers exploited this vulnerability to gain access to Internet facing systems within the organisation. Once in the network, attackers gained root access. Custom tools were then created to allow lateral movement within the network, and to search for sensitive data. 

Cisco Expressway is a collaboration gateway which allows remote employees, partners and third parties to access enterprise communications such as video calling, phone calling and instant messaging. As external users can connect to internal systems, vulnerabilities within these systems can pose a significant risk. The vulnerability was assigned the ID CVE-2026-76466, and has a CVSS score of 9.8. It allows unauthenticated attackers with network access to execute arbitrary commands with root privileges. 

This affects Expressway Core and Expressway Edge systems, both in virtual and hardware appliance form. However, this is only applicable to systems which are in ‘cluster’ configurations. This vulnerability was disclosed by Cisco on 21st October 2026. It exists within the Expressway database service component and relates to cookies being stored persistently. If an attacker can gain access to these cookies, they can access the database service and execute certain remote procedure call commands. 

This allows command execution with root privileges within the underlying operating system. Cisco published a patched version of Expressway (X15.5.20). No workarounds are available. Customers using versions before X15 should upgrade to a patched version to resolve this vulnerability. Although Cisco’s initial advisory stated that there was no public announcement of exploit code or exploitation, exploit code was published on GitHub. The incident detailed by F6 occurred shortly after this exploit code was published. 

Attackers exploited two Internet facing Cisco Expressway systems running version X15.5.3. Attackers then laterally moved to two other cluster nodes within the internal network, using one compromised system. Once root access had been obtained, attackers began creating tools to allow lateral movement. Custom tools were created in Python to allow scanning of network infrastructure, discovery of Server Message Block (SMB) resources, and interacting with Microsoft SQL Server and Windows Remote Management (WinRM). 

The tools were also used to search GitLab repositories. This suggests attackers were attempting to find credentials or sensitive data within the system. Throughout the attack, F6 observed that attackers made changes to their scripts. Comments within the code, and descriptions of changes made within the scripts, suggest that an AI assistant may have been used to create/modify the tools. F6 has not identified which organisation was impacted, or linked this incident to any known threat actors. 

They have however provided some indicators of compromise (IPs and file paths) to assist defenders in investigating whether they may have been compromised. F6 also recommends checking the Erlang system log on Expressway systems for evidence of exploitation. If organisations cannot apply the patch immediately, F6 recommends limiting access to TCP ports 4371 and 4372 in the firewall. Only trusted cluster node IPs should be allowed to connect. This is not an officially recommended workaround from Cisco. In the long term, it is recommended to upgrade to a patched version.

Major Financial Firms Disclose Data Exposure Following Third-Party Security Breach


After a cyberattack on a third-party service provider, JPMorgan Chase, Visa, and Mastercard disclosed a customer data exposure incident. A spokesperson from each company stated on Thursday, November 19, that attackers gained access to limited customer information, including names and email addresses, stored by an external vendor. However, it is noted that their internal systems and payment networks have not been compromised. 

A preliminary investigation by JPMorgan Chase indicates that attackers accessed marketing-related information maintained by certain of the company's service providers. The exposed data may include customer names and email addresses. As a result of the incident, the bank has clarified that it did not impact its banking services and that customers' transactions were not disrupted. 

According to a spokesperson for the bank, affected customers will be contacted directly. Further assistance will also be provided, including complimentary credit monitoring services, where appropriate. Furthermore, the company clarified that the data exposure was unrelated to technical problems reported by some customers earlier in the week, which were caused by a software defect that affected the transaction processing process. 

According to Visa, the allegations are related to a security breach involving a third-party service provider in Asia-Pacific. The company maintained that its own infrastructure remained secure and that no payment-related information, including card numbers, had been accessed. Mastercard also confirmed that it had recently been made aware of an incident involving an external service provider. 

According to the company, a limited number of email addresses belonging to a small group of cardholders enrolled in a particular benefit program were exposed as a result of the breach. This information was classified by MasterCard as non-payment data and the payment network remained unaffected. The disclosures followed the announcement of the hacker group N0n's claim to responsibility on November 16, 2017. 

In its leak website, the group claims to have published files containing customer-related information related to all three financial institutions. There is rumored information that the attackers offered for download was accompanied by a list of three companies as organizations that had not paid. As a result of the incident, financial institutions are exposed to security risks associated with third-party service providers, particularly when external companies are involved in marketing activities and customer information management.

It is reported that the exposed data does not include payment credentials, but it is still possible to target targeted phishing campaigns and conduct social engineering attacks based on customer contact information. Especially within the financial services industry, where external providers often manage customer engagement, marketing campaigns and benefit programs, this incident has highlighted the risks associated with third-party data handling. 

The exposed information did not contain payment credentials, but the availability of customer contact information and email addresses could still provide attackers with an opportunity to commit targeted fraud. A sample of the alleged information has been published on a dark web leak site by the ransomware group N0n, who claims responsibility for the intrusion. 

In the material, according to cybersecurity firm SOCRadar, customer and employee email addresses are reported, along with some telephone numbers and postal codes for some records. However, no independent determination has been made regarding whether N0n was responsible for the attack or whether the published data is authentic. There was a reasonable probability that SOCRadar's available evidence suggests that the breach involved a third-party vendor and information related to marketing and cardholder benefits. 

According to the cybersecurity firm, targeted phishing is the most immediate concern for customers affected by this breach. In some cases, attackers may use exposed contact information to send phishing emails or messages impersonating JPMorgan, Visa or Mastercard, which may trick recipients into divulging information such as passwords, banking credentials, or other sensitive information. 

In most cases, attacks are carried out through social engineering rather than exploiting technical vulnerabilities in banking infrastructure. A fraudulent message can appear more credible if it uses legitimate customer details, thus making it difficult for recipients to differentiate genuine communications from malicious ones. 

The information may also be used to prepare follow-up scams, impersonate customer service representatives, and direct victims to fraudulent login pages. Additionally, the breach raises questions concerning the management of information shared with external suppliers by financial institutions. 

Vendor services such as customer communication, promotional campaigns, and loyalty programmes are frequently used by organizations, creating additional places for sensitive information to be protected. It is therefore possible to expose information related to several major companies through a security failure at one supplier, even if their internal networks remain secure.

Security specialists have also stressed how such incidents could negatively affect the reputation of the company. The financial institution itself is generally regarded as liable for protecting customers' information, regardless of whether compromised systems are the property of an external provider. This incident highlights the importance of performing rigorous vendor security assessments, limiting customer access to information, and strengthening authentication procedures to reduce identity-based fraud risks. This incident also emphasizes the importance of protecting personal contact information, especially telephone numbers and email addresses that can be used to perpetrate follow-up scams. 

Cybercriminals may use these details to impersonate banks, credit card providers, or customer support teams and send convincing messages to steal credentials and financial information by impersonating banks, card providers and customer service representatives. Whenever possible, customers are advised to be alert to emails, text messages, and telephone calls claiming to be from JPMorgan, Visa, or Mastercard, especially those requesting account details, passwords, or one-time verification codes. This breach also raises concerns regarding the increasing reliance on external service providers by financial institutions.

The outsourcing of marketing and customer engagement activities can increase operational efficiency, however it also increases security risks beyond the capabilities of the organization itself. Financial companies must ensure that vendors adhere to strict data protection policies, limit access to customer information, and maintain adequate safeguards to prevent unauthorised access to customer information. It is also essential to conduct regular security assessments of third-party systems and monitor them more closely in order to identify vulnerabilities before attackers can exploit them. 

There are still uncertainties regarding the extent of the incident, since the companies have not disclosed the identities of the affected service providers or the exact number of customers affected. Neither the authenticity of the leaked files nor the claims made by the N0n group have been independently verified. 

While the incident had significant consequences for numerous major financial institutions, it illustrates how a security breach at a single external supplier can result in severe data exposure risks, even in the case of secure core banking systems and payment systems.

Ukraine and FBI Arrest Ransomware Gang Linked to $40M Ransom

 

Ukrainian authorities, working with the FBI, have arrested four suspected members of an international ransomware organization allegedly responsible for extorting more than $40.5 million from at least 28 companies worldwide. The arrests followed a two-year joint investigation into a cybercrime network involving at least 27 people from Ukraine, Kazakhstan, Russia, and other countries. Investigators believe the group was connected to a larger network of more than 60 members operating across eight jurisdictions, including former members of the notorious Conti ransomware gang. 

The organization targeted companies in oil and gas, pharmaceuticals, manufacturing, logistics, finance, and critical infrastructure. Before attacking, the suspects reportedly researched each victim’s finances, assets, employees, and IT weaknesses. They then stole sensitive corporate data, encrypted systems with ransomware, and demanded cryptocurrency payments, threatening to publish stolen information if victims refused to pay. According to Ukrainian police, the 28 identified companies paid more than $40.5 million in ransoms, or roughly UAH 1.8 billion. 

Court records cited in the report identify several alleged victims, including Warren Oil Company, Maxxis International-USA, Newpark Resources, and Quantum Health. In the Warren Oil attack, hackers allegedly copied 1.4 terabytes of data and received an 84.5 BTC ransom payment, worth about $5 million at the time. In another incident, the attackers initially demanded $10 million but ultimately received $5 million after negotiations. The report also links the group to the BlackSuit ransomware operation and the Chaos ransomware strain, although authorities have not confirmed the arrested suspects’ individual affiliations. 

A particularly concerning element of the operation was its use of artificial intelligence to impersonate IT support staff. The suspects allegedly used a custom platform that generated AI voice messages and placed fraudulent calls to employees, posing as technical-support personnel. Workers were persuaded to reveal login credentials or install remote-access software such as TeamViewer and AnyDesk. In one case, an attacker reportedly kept an employee on the phone while another accessed the company’s systems, ending the call only after confirming the breach. The group also used fake corporate VPN pages and spoofed phone numbers to obtain credentials and two-factor authentication codes. 

Ukrainian police carried out 66 simultaneous searches across Kyiv and 11 regions, seizing computers, mobile phones, bank cards, nearly $370,000 in cash, and €20,000. Four alleged key members have been formally notified of suspicion and remain in custody, facing charges related to participation in a criminal organization and unauthorized interference with information systems. If convicted, they could receive up to 15 years in prison. The investigation remains ongoing as authorities work to identify additional members of the network and determine their involvement in other cyberattacks.

Docker Hub Leaked Cloud Credentials Exploited Within 8 Seconds of Image Publication

 



Attackers are extracting and exploiting exposed cloud credentials from publicly accessible Docker images within seconds of their publication, according to a four-month experiment conducted by researchers at Stony Brook University. The fastest observed exploitation occurred just 7.86 seconds after an image containing a planted AWS key was uploaded to Docker Hub.

Researchers Billy Tsouvalas and Nick Nikiforakis investigated the activity by publishing 300 instrumented honeypot images across eight public container registries. The experiment examined how quickly automated scanners discover credentials embedded in container images and whether they subsequently attempt to use them.

Conducted over four months, the study involved planting AWS, OpenAI, and Anthropic API keys alongside decoy SSH credentials and database passwords. The researchers also deployed monitoring mechanisms designed to detect different interactions with their images, including image builds, container execution, and shell access.

The findings, presented at the 2026 ACM SIGSAC Conference on Computer and Communications Security (CCS), revealed extensive automated credential harvesting.


AWS Credentials Exploited Within Seconds

Across the experiment, the researchers recorded more than 75,000 image pulls. The planted AWS credentials alone attracted over 140,000 API requests originating from approximately 5,000 unique IP addresses.

The observed requests ranged from preliminary authentication checks to attempts to enumerate available cloud resources. Some interactions progressed further, indicating attempts to consume resources using the exposed credentials.

The earliest recorded AWS API request occurred just 7.86 seconds after an image was published on Docker Hub. The median time between publication and the first API request was 51.19 seconds. Furthermore, all 100 planted AWS keys had been accessed within 15 minutes of publication.

The OpenAI and Anthropic credentials experienced similar abuse. Automated activity rapidly consumed the balances associated with the researchers' test accounts, demonstrating that exposed AI service tokens can also become targets for immediate financial exploitation.

Docker Hub generated almost all observed AWS credential activity, although the researchers also recorded instances of abuse involving Harbor, another container registry included in the experiment.


Automated Scanners Extract Credentials Without Running Containers

The researchers collectively referred to the automated scanning activity as "ContainerBots." However, the designation does not establish that all observed scanners belonged to one threat actor or operated through a centrally coordinated infrastructure.

An important finding concerned how these bots accessed the exposed credentials.

Monitoring systems rarely detected attempts to execute the planted containers, suggesting that attackers generally did not need to run an image to retrieve its contents. Instead, they relied on static inspection techniques, including unpacking image layers and querying registry APIs to retrieve filesystem contents.

This approach allows scanners to examine files stored within container images without launching the applications themselves.

Container images package application code, dependencies, configuration files, and other resources into reusable layers. Consequently, credentials accidentally included during image creation can remain accessible through those layers even when developers do not intend to distribute them.

The researchers explained that their observations overwhelmingly involved static analysis rather than actual container execution.


Docker Hub Secret Exposure Is an Established Problem

The latest findings add to previous research documenting widespread credential exposure across public container repositories.

In December 2025, researchers at cybersecurity company Flare identified 10,456 Docker Hub images containing exposed secrets. These included approximately 4,000 AI-related API keys, alongside credentials capable of providing access to cloud environments, databases, Git repositories, and CI/CD infrastructure.

An earlier 2023 investigation involving 337,171 Docker images identified 52,107 valid private keys and 3,158 distinct API secrets across 28,621 images.

Such exposures create substantial remediation challenges. Removing an affected image or deleting a credential from its configuration does not invalidate copies already retrieved by automated scanners. Organizations must revoke compromised credentials, issue replacements, examine access logs, and assess whether unauthorized access occurred.


Researchers Recommend Additional Docker Hub Defenses

Tsouvalas and Nikiforakis recommend introducing automated secret detection before container images become publicly accessible. Docker Hub could scan uploaded images for embedded credentials and notify publishers when potentially sensitive information is discovered.

They also propose restricting or rate-limiting access to Docker Hub's public feed of recently published or updated images, making large-scale automated collection more difficult.

The researchers told BleepingComputer that they submitted their findings and the complete research paper to Docker in May 2026. Although the company acknowledged receiving the disclosure, they reportedly received no subsequent response.

A smaller experiment conducted in August to determine whether Docker had introduced additional protections did not identify any changes.

Docker's existing documentation already recommends using BuildKit secret mounts rather than passing credentials through Dockerfile "ARG" or "ENV" instructions, which can leave sensitive information in image contents. Secret mounts make credentials temporarily available during specific build operations without automatically persisting them in the resulting image.

The National Institute of Standards and Technology (NIST), in its SP 800-190 Application Container Security Guide, similarly recommends keeping secrets outside container images and supplying them dynamically when required.

The research demonstrates that publishing an image containing an active credential can expose it to automated collection almost immediately. Developers and organizations should therefore treat any credential embedded in a publicly accessible image as compromised, revoke it promptly, and ensure that replacement credentials are not retained in subsequent image layers.

Apache Roller RCE Vulnerability Actively Exploited in Attacks

 

Apache has issued an urgent warning for administrators running Apache Roller after confirming that attackers are actively exploiting a critical remote code execution flaw. The vulnerability, tracked as CVE-2026-129448, affects Roller versions 4.0.0 through 6.1.4 and allows an unauthenticated attacker to execute arbitrary code on a vulnerable server. Apache has released Roller 6.1.6 to address the issue, and organizations that cannot update immediately are being urged to apply temporary mitigation steps. 

The flaw affects Apache Roller, an open-source, Java-based group-blogging server. Although it has a smaller user base than mainstream content-management systems, the issue is serious because it can give attackers full control over affected servers. The vulnerability involves the deserialization of untrusted data through the platform’s XML-RPC endpoint. 

Roller accepts vendor extension types and deserializes them before authenticating the requester, allowing an attacker to send malicious data that the server processes before checking whether the sender is authorized. This unsafe sequence can lead to arbitrary code execution, enabling attackers to run commands, install malware, steal data, or use the compromised server for further attacks. 

Apache has confirmed that CVE-2026-129448 is being exploited in the wild, although it has not disclosed details about the attackers, the scale of the campaign, or how many systems have already been compromised. The company also noted that the flaw is the same underlying issue as CVE-2026-82384, which had previously listed only Apache Roller 6.1.5 as affected. The confirmation of active exploitation raises the urgency considerably. Organizations running Roller should assume that internet-facing instances may be targeted and should prioritize patching over routine maintenance. 

The most effective response is to upgrade to Apache Roller 6.1.6 or later. The updated release disables the vulnerable extension types and rejects malicious XML-RPC requests after turning off the XML-RPC feature, closing the path attackers are using to exploit the flaw. Administrators who cannot upgrade immediately can reduce exposure by setting enabledForExtensions to false in WEB-INF/web.xml, removing the /roller-services/xmlrpc servlet mapping, and restarting Roller. These steps block the vulnerable functionality while a permanent update is prepared.

Apache specifically warns that disabling XML-RPC through the administration interface is not enough on older versions, because affected Roller builds deserialize incoming requests before checking whether the XML-RPC setting has been turned off. This means an administrator may believe the service is disabled while the server remains exploitable. 

The Roller flaw arrives amid a broader run of Apache security issues, including a recent critical vulnerability in the HTTP/2 module of Apache HTTP Server that could also allow unauthenticated attackers to achieve remote code execution. Since November 2021, CISA has added 41 Apache flaws to its catalog of vulnerabilities exploited in the wild, and eight of those have also been abused by ransomware gangs. Organizations should inventory their systems, identify any Roller installations, and treat this vulnerability as an immediate security priority.

How Do Spam Callers Get Your Phone Number? The Hidden Sources Behind Unwanted Calls

Many smartphone users are experiencing unwanted calls from unknown numbers, ranging from promotional messages and automated marketing calls to fraudster scams designed to steal money and personal information. 

The majority of calls originate from databases containing telephone numbers collected from online and offline sources, although some are generated by random dialing systems. There is a growing market for the collection, organization, and sharing of personal information among businesses and third parties as consumer information becomes increasingly valuable. 

When users register on a website, complete online forms, install mobile applications, shop online, or enter promotional contests, you can reveal your contact information to several organizations. There is also the possibility that this information may circulate through third-party data-sharing arrangements or be made available following a data breach. 

As one of the lesser-known players in this ecosystem, data brokers are able to collect information from multiple sources and create consumer profiles that can then be sold to advertisers, marketing firms, and other interested parties. It is therefore possible to reach businesses and individuals through a number shared for ordinary services or registrations without any direct connection to the original source, for example. Cybercriminals can use such information to conduct targeted spam campaigns, impersonation scams, and financial fraud. 

How Phone Numbers Find Their Way Into Spam Lists

The majority of spam calls are not the result of stolen databases. Some are reached using automated dialing systems that generate and call random combinations, while others are acquired from publicly available records, such as business directories, property documents, and online listings. 

The commercial distribution of consumer information remains an important source of unwanted phone numbers, however. A number of methods are commonly employed to collect phone numbers, including registration forms, online purchases, loyalty programs, surveys, promotional offers, and account sign-ups. 

If a user provides their contact information, the company may share it with advertising partners or other third parties in accordance with the company's data sharing policy. There are instances where consent is buried in lengthy terms and conditions or presented in confusing opt-in settings, causing confusion about where the information will end up. As part of this process, data brokers play a key role. They combine information gathered from various sources including websites, public records, purchase histories, social media activity, and commercial databases to create consumer profiles. 

Marketing agencies, businesses, and other organizations can purchase or license the resulting lists. Despite the fact that most of this activity occurs within the advertising industry, poorly controlled data-sharing practices can also make contact information available to scammers. It is also possible to expose customer information through breaches of security and phishing attacks. 

When a security breach occurs, customer records may include telephone numbers, names, email addresses, and other personal information when an online service suffers a security incident. As an alternative to using legitimate websites, cybercriminals can also retrieve information through the use of fake job advertisements, fake login pages, and malicious applications. 

By using automated tools known as web scrapers, some phone numbers can also be harvested directly from websites and social media platforms. Once a number has been scanned and extracted in bulk, it can be added to calling lists or combined with other personal information to make fraudulent calls appear more convincing. 

Although it is important to distinguish between legitimate data collection and criminal activity, these two concepts can intersect when personal information is shared widely, inadequately protected, or exposed by security flaws. 

Ultimately, a number that was originally provided to register for a shopping account or service may become part of a database that is used to sell unsolicited information or perpetrate targeted scams. 

How to Keep a Phone Number Away From Spammers

A person can minimize their chances of receiving unwanted calls and targeted scams by limiting the exposure of their personal contact information, even though preventing every spam call may not be possible. The first step to preventing unwanted calls and targeted scams is to be selective when sharing personal contact information. It is important to be cautious when dealing with unfamiliar websites, suspicious registration pages, fraudulent job portals, and promotional offers requesting unnecessary personal information. 

When submitting information to a website, you should check the reputation and privacy policies to identify questionable services. Public exposure should also be considered. It is important to remove phone numbers from public social media profiles, online directories, and other platforms whenever possible. Mobile users should review application permissions on a regular basis, particularly access to contact information, location, photographs, and other personal information. 

A user can revoke unnecessary permissions through the privacy settings on Android and iOS devices. Reviewing account privacy options as well as avoiding unnecessary third party sign-ups can also help limit data sharing. For users already receiving frequent unwanted calls, built-in spam detection features and call-blocking services can assist in filtering out suspicious numbers. 

In order to avoid answering unknown calls immediately, you can place them into voicemail. It is important to avoid giving passwords, banking information, OTPs, or remote access to devices to suspicious callers, regardless of their claim to represent a trustworthy organization. A user should also check whether their personal information has been exposed in known data breaches. 

Services such as Have I Been Pwned can be used to identify exposed email addresses corresponding to compromised accounts, while searching online may reveal information that can be accessed by the public. The primary cause of spam calls is not always careless sharing. Random dialing, commercial data collection, and security breaches can expose numbers without the owner being aware of them. 

Spammers and cybercriminals may have a harder time converting ordinary contact information into opportunities for fraud if privacy practices are strengthened, app permissions are handled carefully, and unsolicited calls are made more aware.

Featured