InfoSecBulletin Cybersecurity for mankind
Malyasian National Cyber Security Agency (Nacsa) is investigating a possible data breach that exposed the data of four million U Mobile subscribers.
The data, which claimed to contain personal information like names, addresses, MyKad numbers, andThe data, which may include personal information like names, addresses, MyKad numbers, and mobile phone numbers, was put up for sale on July 16 for US$5,000 (RM23,380) in Bitcoin on a well-known forum that sells leaked information.
Hacker claim Leak of Deloitte Source Code & GitHub Credentials
CISA Issued Guidance for SIEM and SOAR Implementation
Linux flaws enable password hash theft via core dumps in Ubuntu, RHEL, Fedora
Australia enacts mandatory ransomware payment reporting
Why Govt Demands Foreign CCTV Firms to Submit Source Code?
CVE-2023-39780
Botnet hacks thousands of ASUS routers
Bangladesh Bank instructed using AI to prevent online gambling
251 Amazon-Hosted IPs Used in Exploit Scan for ColdFusion, Struts, and Elasticsearch
Zero-Trust Policy bypass to Exploit Vulns & Manipulate NHI Secrets
Evaly E-commerce Platform Allegedly Hacked
However, the posted sample looked incomplete, with some entries missing MyKad numbers and addresses.
Nacsa, the government agency in charge of cybersecurity in Malaysia, is investigating the data’s legitimacy and has asked U Mobile for more details.
In a statement, U Mobile said “it’s aware of the alleged data breach. It said: “We are actively investigating this situation. We are working closely with the authorities to address this matter effectively and will provide relevant updates once confirmed information becomes available. We wish to assure all stakeholders that we take matters of cybersecurity and data privacy seriously and are dedicating all resources to thoroughly investigate the situation.”
(Media Disclaimer: This report is based on research conducted internally and externally using different ways. The information provided is for reference only, and users are responsible for relying on it. Infosecbulletin is not liable for the accuracy or consequences of using this information by any means)
