North Korean cyber-espionage group Kimsuky appears to be moving beyond occasional use of public AI services by assembling a local artific...
“The strongest pattern in the first half of 2026 was the way different threats converged around trust. Scams, account takeovers, malicious packages and AI agents all moved closer to the systems, workflows and permissions people already rely on,” said the report.
46% of Gen threat findings were scams, whereas malvertising amounted for 30%. Gen stopped 114.2 million e-commerce scams and 20.3 million tech support scams.
These numbers are important, but they fit different kinds of scams into a few categories. A discovery does not reveal how the first trap became script execution, or how the script turned into a proxy change or browser, or how a wallet address was changed before the target verified a transaction.
Two H1 investigations should be looked at in-depth. The first is a banking-malware campaign initiated with hacked corporate mailboxes and finished with browser manipulation and proxy.
In the second finding, a cryptocurrency campaign deployed a Rust-based clipper and got C2 infrastructure pointers from Binance Smart Chain.
The payloads are distinct, but none of the campaigns relied on breaking the genuine system at user end. The banking malware used a genuine account to set the trap whereas the clipper allowed the blockchain record an authentic transaction after modifying the local destination address.
The banking campaign attacked users in Lithuania, Poland, Slovakia, and Czechia. The lures appeared to be genuine business emails such as invoice messages, scanned document verifications, and shipment notices.
In various incidents, the texts were sent from hacked corporate mailboxes. The email was not designed to appear as if it came from an authentic organization. The emails were sent from an authentic account that threat actors had already hacked.
DKIM and SPF can still sail through when a message is sent via genuine infrastructure, whereas reputation systems may spot a sender with an authentic history.
The attachment deployed a JavaScript dropper, and then the chain travelled via PowerShell stages before reaching banking functionality and shellcode. The available signs indicate at GepyS.
The malware changed proxy settings and deployed a browser add-on, positioning itself nearby to the target’s banking session.
Bank of Baroda has confirmed a cybersecurity incident involving a compromised employee email account after reports emerged that nearly 1TB of data allegedly linked to the state-owned lender had been published on the Dark Web.
The bank said the compromised account resulted in unauthorised access to certain data, but clarified that its core banking systems were not accessed and continue to remain secure. It said the incident was identified promptly, containment measures were implemented, and a comprehensive forensic investigation has been launched in coordination with relevant authorities.
The confirmation followed reports from the X account DailyDarkWeb and cybersecurity researcher Srikanth Lakshmanan, founder of CashlessConsumer, who flagged an alleged large-scale data dump connected to Bank of Baroda.
According to the claims, the dataset contains personal and corporate banking records, including savings and current account information, loan records, NetBanking users, NRI and corporate banking services, customer-support documents, and records linked to branches and ATMs. Reports from researchers also said the material included customer details, identification documents and internal audit records.
Samples and download links were reportedly shared alongside the threat actor's claim of possessing approximately 1TB of data.
However, the size of the alleged dataset has not been independently established by Bank of Baroda. Reuters reported that the Dark Web listing was advertised as a cache exceeding 700GB based on metadata analysis conducted by Lakshmanan. The number of customers whose information may have been exposed also remains unknown.
This distinction is important. The appearance of a large archive online does not, by itself, establish that every file originated from Bank of Baroda or that the entire advertised volume was successfully exfiltrated from the bank.
What allegedly appeared in the data dump?
The initial claims described a wide range of banking information. This reportedly included savings and current account records, loan-related documents, NetBanking information, NRI and corporate banking records, customer-support material, and branch and ATM data.
Other reports said samples contained highly sensitive information such as Aadhaar details, customer names, loan documents and other identity-related records. Some reports citing the claims placed the number of customer application forms potentially involved between 100,000 and 300,000. These figures remain allegations and have not been confirmed by Bank of Baroda.
Lakshmanan also shared screenshots that he said showed the root folder of the alleged data dump and reported that the download link was active. He described the incident as a "cyber disaster" and called for the Reserve Bank of India (RBI) and National Payments Corporation of India (NPCI) to consider disconnecting the bank's systems while the extent of the compromise was investigated.
At the time of those warnings, the source and method of the alleged data theft were unclear.
Bank of Baroda's subsequent statement has now provided an important piece of that picture.
Employee email account was the confirmed entry point
According to the bank, the confirmed incident involved the compromise of an employee's email account. The account was then used to obtain unauthorised access to certain data.
Bank of Baroda has not disclosed how the email account was compromised, what specific files were accessed, or whether all of the data advertised on the Dark Web originated through that account.
The lender has, however, clearly stated that its core banking systems were not accessed and remain secure.
That distinction matters because compromising an employee's email account is not the same as compromising the systems that process customer transactions.
At the same time, an email account inside a large financial institution can provide access to highly sensitive material. Depending on the employee's role and permissions, an account may contain customer correspondence, loan documents, identity records, internal reports or links to shared resources.
The incident therefore demonstrates how an attacker may be able to obtain valuable financial information without directly breaching the core platform responsible for banking transactions.
Customer risk extends beyond stolen funds
There is currently no public evidence that the alleged incident allowed attackers to directly access customer balances or manipulate transactions. Bank of Baroda has specifically said that its core banking systems were not accessed.
The potential exposure of personal and financial records nevertheless creates a separate risk.
Information such as customer names, identity documents, account-related details and loan records could give criminals material for highly targeted phishing and impersonation attempts. A scammer with genuine information about a customer's banking relationship can make fraudulent calls, emails or messages appear far more credible.
Customers should therefore be particularly cautious of communications claiming to originate from Bank of Baroda and requesting OTPs, passwords, PINs, card information or remote access to devices.
The reported leak should not automatically be interpreted as evidence that customer funds have been compromised. The more immediate concern, if the exposed records are genuine, is the possibility of follow-on fraud using information that customers would normally expect their bank to protect.
Forensic investigation now underway
Bank of Baroda said it has initiated a comprehensive forensic investigation to establish the nature and extent of the incident. The bank also said it is working with relevant authorities in accordance with applicable regulatory requirements.
Several key questions remain unanswered.
Investigators will need to determine how the employee's email account was compromised, what information was accessible through it, how much data was actually accessed or exfiltrated, and whether the Dark Web archive corresponds to the confirmed incident.
The investigation will also need to establish how many customers, if any, were affected.
The incident has already generated financial implications for the lender. The Economic Times reported that Bank of Baroda notified a preliminary cyber-insurance claim under a programme with total coverage of approximately ₹750 crore, with National Insurance Company serving as the lead insurer. The notification is an intimation of loss while the forensic investigation continues and does not represent a confirmed ₹750 crore loss.
The financial consequences of a data breach can extend beyond direct theft. Forensic investigations, remediation, legal costs, regulatory responses, customer support and other incident-response expenses can all contribute to the eventual cost.
Regulatory questions remain
The incident also places renewed attention on cybersecurity controls within India's banking sector.
CERT-In's directions under Section 70B of the Information Technology Act establish requirements for information-security practices, incident response and cyber-incident reporting.
Bank of Baroda has said it is cooperating with relevant authorities, although the public details of its regulatory notifications have not been disclosed.
For now, the most important distinction is between what has been confirmed and what remains alleged.
Bank of Baroda has confirmed that an employee's email account was compromised and that the incident resulted in unauthorised access to certain data. It has also confirmed that its core banking systems were not accessed.
The claim that approximately 1TB of Bank of Baroda information was leaked, the precise contents of the Dark Web archive, and the number of customers potentially affected remain subject to investigation.
What began as an alarming Dark Web claim has therefore evolved into a confirmed security incident with an unresolved scope. The forensic investigation will determine whether the reported hundreds of gigabytes of banking information represent the full extent of the compromise, a smaller subset of genuine Bank of Baroda data, or a mixture of both.