Cyberattack Nigerian banks: what customers must be told
When a cyberattack hits Nigerian banks, customers worry less about how the attackers got in than about what it means for them. They want to learn whether their funds are secure, whether their personal details have leaked, and which measures they ought to adopt to protect themselves.
The content of a Nigerian bank's disclosure after a cyberattack Nigerian banks may suffer turns partly on what kind of incident has occurred and partly on the audience that needs to hear about it. Notifying the Central Bank of Nigeria (CBN) of an incident is one thing, warning affected customers is another, and neither of them automatically means making a public announcement. Yet when a personal data breach is liable to pose a serious risk to individuals, banks are legally bound to tell those people.

This difference matters more and more, because financial institutions now face attacks capable of leaking customer data, interrupting services or putting funds at risk. With every cyberattack Nigerian banks endure, regulators are left with a hard problem: how to compel banks to make incidents public without letting each announcement undermine public confidence.
What fraud has cost Nigerian banks
CBN data show that ₦134.48 billion ($100.09 million) was lost to fraud by Nigerian lenders along with those who bank with them between 2020 and 2025. The totals capture what victims lost, not money that may have left the wider banking system, and they do not separate any cyberattack Nigerian banks face on their infrastructure from other types of fraud. Newer figures from the Nigerian Interbank Settlement System put payment fraud losses at ₦25.85 billion ($19.24 million) in 2025, down from ₦52.26 billion ($38.90 million) the year before.
Neither set of figures reveals the number of cyberattack Nigerian banks have experienced, nor how frequently customers were never told that their data had been exposed. Even so, they highlight the stakes in an economy in which confidence in the financial sector underpins everyday transactions.
Regulators are not customers
The CBN's 2024 Risk-Based Cybersecurity Framework requires commercial lenders, along with payment service providers holding banking licences, to report any security incident to the Director of Banking Supervision inside 24 hours. That lets the supervisor weigh up threats, keep watch over the institutions under its oversight and coordinate responses jointly. The rule does not demand that every cyberattack Nigerian banks suffer be made public.
Festus Amede, who chairs the Committee of Chief Information Security Officers of Nigerian Financial Institutions, said: “Banks are disclosing attacks currently to regulators, and if any bank fails to, they face sanctions from regulators.” Whether any bank has previously been sanctioned for concealing a cyberattack Nigerian banks reported late, or not at all, was not something he addressed.
Still, what a regulator wants to know is not what a customer wants to know after a cyberattack Nigerian banks have faced. The CBN might require the technical particulars of an attack, the systems it touched and how the bank reacted. Customers, by contrast, want to learn whether their funds or private details are in danger, and what action they ought to take.
It follows that a bank may inform the CBN of an incident, such as a cyberattack Nigerian banks have to report, while saying nothing publicly. Likewise, meeting that duty to the supervisor does not automatically discharge a distinct obligation to alert those customers whose private information has been laid open.
What the data protection law requires
The second duty comes from the Nigeria Data Protection Act 2023. Under s. 40, a data controller has 72 hours from the moment it learns of a breach to tell the Nigeria Data Protection Commission (NDPC), where that breach could endanger people's rights and freedoms. If a cyberattack Nigerian banks suffer could leave individuals facing grave danger, those affected must also be informed, and without delay.
This difference is important. An attempted intrusion does not always expose personal information, and data breaches differ in how risky they are. According to NDPC guidance, signs of high risk include possible identity theft, fraud, and sensitive personal data being laid bare. Judging the risk turns on what information was involved and what consequences are likely, rather than on whether the event is labelled a cyberattack Nigerian banks have reported.
Disclosure versus panic after a cyberattack
The difficulty for banks lies in how to keep customers informed during a continuing investigation. Saying too little may leave customers vulnerable. Saying too much too early may sow confusion or damage trust before the bank has worked out what actually happened.
Gbenga Sesan, who leads Paradigm Initiative as its executive director, says the danger of causing panic is no excuse for banks to keep customers in the dark. Paradigm Initiative is an organisation operating across Africa that focuses on rights and access in the digital sphere. In his view, a bank should first make sure the incident has been contained or is being dealt with, and only then tell customers what occurred and how it is responding.
“They need to manage the balance between panic and disclosure,” he told TechCabal.
Handling this well matters even more once personal data is at stake. Even if the money in a customer's account has not been touched, that person can still be exposed if a hacker has got hold of a phone number, an e-mail, or other details that might be used to impersonate them or to mount phishing attempts.
“The affected individuals need to be notified, with the bank stating which data was compromised and at the same time confirming what actions have been and will be taken,” Sesan said.
A notification has to describe what the breach may well cause, what has been done or is planned to deal with it, and where those affected can get further information. A general assurance that customers' money is safe may therefore not be enough when their personal details have been exposed.
Why a bank run is the worry
Iyinoluwa Aboyeji, who is a co-founder and general partner at Future Africa, points to another risk. Because customer confidence can decide whether people keep their money with a bank, he fears that going public about an attack could set off withdrawals and make the harm from the cyberattack worse.
“Right now there is no upside except a run on the bank,” he said.
Aboyeji's view is that banks ought to give more weight to preventing attacks and recovering from them, for instance through cyber insurance, which can help an institution cope with the financial fallout of an attack. He also cautions that a regime fixated on punishment might make banks reluctant to report incidents at all.
“Punishment will make it less likely they disclose a cyberattack, not more likely,” he said.
His point highlights a tension within this discussion. Lenders need reasons to report attacks quickly, yet customers also need safeguarding from institutions that may be tempted to protect their reputations instead of owning up to a breach. Transparency cannot be left optional as the solution. Equally, not every incident, whatever its nature or impact, should be read as proof that an institution has failed.
Regulators need to tell apart two kinds of bank: one that discloses an incident, shuts down the threat and honours its duties, and another that skimps on fundamental security or holds back information the law obliges it to hand over.
Recent cases of cyberattack on Nigerian banks and fintechs
Several recent cases show why it matters what kind of cyberattack has taken place. Zenith Bank told its customers in August 2026 that intruders had gained access to a small amount of contact details, among them mailing addresses and telephone numbers. According to the bank, its central banking platforms and online services remained secure.
Lendsqr made public in November 2026 that it had faced attempted cyberattacks. Its CEO, Adedeji Olowe, stated that the firm's protective measures held firm, and that no money, user information or accounts had been compromised. In 2023, the crypto exchange Patricia reported a security incident touching Bitcoin and Naira holdings. Later reports placed the incident in January 2022 and put the losses at roughly $2 million.
Such cases cannot be treated as the same thing. Each of the following brings distinct consequences, and may set off distinct duties:
- a failed attempt to attack;
- the exposure of customer details;
- an outright theft.
A bank may suffer a grave security incident while no customer data is compromised. By the same token, no money having been stolen does not necessarily imply that customers have nothing to worry about.
Enforcement and what customers can expect
In Sesan's view, the difficulty goes further than whether banks send out notices within the set deadlines. Regulators have to determine whether institutions are correctly recognising incidents and taking action on what they find. He said banks keep internal security records, and these can help supervisors judge whether incidents were spotted and reported.
“The notification is only a part of the measures taken to ensure transparency and ensure that action follows,” he said.
He contended that the true measure of the rules is how well they are enforced, remarking: “The framework is only as strong as its implementation, and the latter is where we lack.”
Regulators, then, carry duties that go further than simply collecting incident reports. They are expected to check that institutions are complying, order fixes where they are needed, and state plainly when a bank has fallen short of what is required of it. Publishing figures on how many incidents occur, what kind they are, where compliance has failed and which enforcement steps were taken would make institutions more answerable. It need not reveal sensitive technical information or jeopardise investigations.
From the customer's side, what matters is more straightforward. People want to find out if their funds or private data are in danger, how the bank has limited the damage, and what action they ought to take themselves. Support should be easy to reach, and they should receive fresh updates whenever the investigation alters what is understood about the breach.
Nobody is suggesting that each cyberattack on Nigerian banks should turn into a public spectacle. The goal is to stop banks from hiding behind worries about causing a stampede to justify keeping back what customers require to hear. Where a financial system rests on trust, staying quiet may shield a bank's reputation for a time. Yet it may also leave depositors bearing risks that they never had a fair opportunity to manage.




