BLACKOUT MAP

Security ·

Why hackers will never wipe out your debt

Share
Updated 17 November, 12:47 UTC
  • First version.

On 16 November, malicious code ran on the websites of 178 organisations, from Zoom and the BBC to HSBC and Equifax. Under the news, one reply with half a million views summed up what a lot of people were thinking: "everything but credit card debt and student loans". It's a good joke. It's also exactly right, and not because the hackers were unlucky. This is why no hack is ever going to wipe out what you owe.

What actually happened on 16 November

Many big websites use Optimizely, a tool for testing different versions of a page. The website loads a small script from Optimizely, and whatever that script says, your browser runs. Someone got the ability to change those scripts. According to Scott Helme of the security firm Report URI, who found it, 188 of the 1,611 Optimizely scripts his team checked carried malware, belonging to 178 organisations. Banking and finance was the biggest group, with 32 of them.

The malware ran in the visitors' browsers. It:

  • copied card numbers, expiry dates and CVV codes typed into a site's own payment forms (payment boxes run by a separate payment company were out of its reach),
  • took cookies and screenshots of the page,
  • swapped cryptocurrency wallet addresses for the attacker's own, which collected about $7,150 before it was emptied,
  • tried to break into older iPhones and iPads with two known exploit kits.

HSBC's site had a security policy that blocked the main malicious script, but a backup copy hidden inside the snippet still ran. Optimizely says it has fixed the vulnerability and removed the injected code.

Notice what is missing from that list. The attack never reached a bank's accounts. It sat on the public website, the same layer as the pictures and the menu. The bank's ledger, where your balance actually lives, is a different system that the website only asks questions. So the first reason this hack didn't touch anyone's debt is simple: it was never anywhere near it. It was built to take money from visitors, not to give any back.

If you used one of these sites on 16 November: check your card statements for payments you don't recognise, and update your iPhone or iPad. According to Report URI, iOS 18.7.3 and newer, and iOS 26.3 and newer, are safe from these exploit kits.

A debt is a contract, not a number in a database

Suppose an attacker did get all the way in. It still wouldn't work, because the number on your screen is only a record of the debt. The debt itself is a legal agreement. You agreed to the card's terms when you opened the account. For a federal student loan in the United States, you signed a Master Promissory Note, and the Department of Education holds more than $1.6 trillion of those loans for over 40 million people.

If every record of your balance vanished tomorrow, the agreement wouldn't vanish with it. The lender would have work to do to show what you owe, but nothing about the loss means you owe less. And in practice the lender doesn't have to rebuild anything from memory, because your debt is written down in many places at once.

Where one credit card balance is written down

a simplified picture, details differ per bank and country
The bank's websiteWhat the 16 November attack reached. Your balance isn't stored here.
The bank's main ledgerThe system that actually keeps your account.
A live copy elsewhereA second data centre that follows every change.
BackupsDaily copies, some on storage nobody can rewrite.
Tape and outside vaultsOffline copies, often at another company.
The card networkVisa, Mastercard and the processors saw every purchase.
Credit bureausEquifax, Experian and TransUnion get your balance every month.
Auditors and regulatorsReports on the bank's loans as a whole.
Your own inboxStatements, the agreement you accepted, payment receipts.
To make a debt disappear, someone would have to change all of these so they agree with each other, without anyone noticing the gap.

How banks keep their copies out of a hacker's reach

Backups that sit next to the system they protect are not much use: ransomware gangs look for them first, so they can delete or encrypt them before demanding money. Financial companies answer that in a few layers.

  1. Copies the main system can't reach. In the usual setup, a server sends its data to the backup machine, so it also holds the key to it. The safer way turns this around: the backup server connects, copies the data (with a tool like rsync, for example) and leaves, and the main server has no way back in. Some setups only open the connection while the backup is running.
  2. Storage that can't be rewritten. Some copies are written to storage that refuses changes and deletions until a set date, even from an administrator. In the United States, the SEC's rule 17a-4 has required this kind of storage for brokers' records for decades; since 2022 they may use a full audit trail instead, as long as the original can always be re-created.
  3. Tape on a shelf. Tape sounds old-fashioned, but it is booming. A cartridge on a shelf has no network connection, so nothing online can touch it. Tape makers shipped a record 176.5 exabytes of capacity in 2024, 160.3 in 2025, and 57% more in the first quarter of 2026 than a year earlier.
  4. A vault somewhere else. In the US, many banks and credit unions take part in Sheltered Harbor, an industry standard created for exactly the "what if everything is wiped" case. Every night, each one stores its customers' account data in a standard format, encrypted, in a vault that is cut off from its own systems and can't be changed. Some partner with another bank to hold each other's vaults. Every participant is audited each year and has to test that it can actually restore.
  5. The law asks for it. In the European Union, the Digital Operational Resilience Act (DORA) applies to banks and insurers since January 2025. Its rule on backups says that when they restore from their own systems, they must use systems that are physically and logically separated from the original.
  6. Paper still exists. Some agreements are still signed on paper and kept. Most are signed online now, but an electronic signature is just as binding, and the signed record is one more copy that lives outside the bank's main system.

Who opens the connection matters

two ways to make the same backup

Push: the main server sends its data

Main serverhas the backup password
Backup server

A hacker who takes over the main server also has its key to the backups, and can delete or encrypt them too.

Pull: the backup server fetches the data

Main serverno way in
Backup serverlogs in, copies, leaves

The main server has no login on the backup machine. Taking it over gives an attacker nothing to reach the copies with.

The pull method is a common pattern, not a rule, and banks don't publish how theirs is built. The idea behind it, keeping the copy out of reach of the system it protects, is what regulators now ask for.

When banks really did get hacked

This isn't theory. Banks and lenders have been badly hit, and debts never disappeared:

  • ICBC, November 2023. Ransomware hit the US arm of the world's biggest bank. Its systems were so cut off that settlement details for US Treasury trades were reportedly carried to other firms on a USB stick by a messenger, and its parent put $9 billion into the unit to cover trades that hadn't settled. Messy, expensive, and nobody's obligations were wiped.
  • Equifax, 2017. One of the three big credit bureaus lost the personal details of about 147 million people. People's debts stayed exactly where they were. What changed was that criminals could now open new credit in their names.
  • Nelnet, 2022. A student loan servicing company had the names, addresses and Social Security numbers of about 2.5 million borrowers stolen. The loans were untouched. The borrowers got credit monitoring.

And if an attacker did change a balance, the bank would find out. Banks check their records against each other and against outside parties every day, so a loan that suddenly drops to zero shows up as a gap. That gap gets treated as fraud, the balance is restored from one of the copies above, and the account whose debt vanished is the first one anybody looks at.

So who loses when a bank is hacked?

Usually, you do. Look at the pattern: card numbers skimmed, crypto redirected, iPhones attacked, personal details stolen. Hacks take from customers. They don't set them free. The reply on 16 November was right, and it will stay right for the next attack too.

If a debt is too heavy, the ways out are slow and boring: talking to the lender, official repayment and forgiveness programmes, or a non-profit debt counsellor. None of them make headlines, but unlike a hack, they actually change what you owe.

Sources

Share this article

Blackout Map is a live map of internet outages and shutdowns around the world. Open the map · Security watch · RSS · Follow us on X: @Blackoutmap_net

All articles

Keep reading

Security · 15 Nov 2026Scrapers that never use the same address twice, and how we stop them without CAPTCHAsResidential proxy networks send each request through a different person's home internet, so blocking addresses is useless. How we spot them by network instead, what a one-second JavaScript check does, and what it still can't stop. Security · 21 Oct 2026 16,530PHP2Shell: what we know about the two critical PHP flaws (now exploited)Two critical flaws in PHP, the language behind about 70% of websites, can let anyone run code on a server with one request. The fix is out and attacks are confirmed: how the attack works, what is confirmed, what to do, and what it could mean for the internet. Explainer · 21 Oct 2026 239Can a software flaw take the internet down?Ten years after the Mirai attack on Dyn: how security flaws turn into outages, the times they did, and what Blackout Map can and cannot see.

More from the blog

Security · 12 Nov 2026 135Apache's HTTP/2 flaw: found twice in eight days, fixed in 2.4.71CVE-2026-119618 is a race in Apache's mod_http2 that can let an attacker run code without logging in. Only servers with HTTP/2 on are affected. Who found it, who is at risk, the dispute over an exploit, and what to do. Outage · 10 Nov 2026Internet partial outage in Central African Republic: what we measuredBlackout Map measured an internet partial outage in Central African Republic from 20:45 UTC on 7 November 2026. What the data shows, and how to follow it live. Security · 6 Nov 2026 352How one asterisk opened a door in OpenSSH: the *sshole bug, explainedCVE-2026-123158 lets a 257-character password into accounts that have no password, on Alpine and other musl systems. How three sensible fixes built it, who is really affected, what some reports get wrong, and what to do. Analysis · 6 Nov 2026 125Is 72 hours of supplies enough? What 93 nationwide power outages showCanada and the UK tell people to be ready for three days without power. We measured 93 nationwide outages since 2022: nine in ten ended within three days. The eight that didn't were all on islands, and local storm damage can take weeks to repair. Fact check · 5 Nov 2026 1,906Every "global blackout" date so far, and what really happenedA running list of viral global blackout dates: what was claimed, what was real, and why it can't happen that way. Includes 13, 17 and 18 November 2026, with the live status of the internet. Analysis · 5 Nov 2026Election shutdown watch: where the internet could be cut nextThe next elections to watch for internet shutdowns, starting with Cabo Verde, The Gambia, Guinea-Bissau and South Sudan, with each country's live internet status and what happened at this year's votes. Security · 3 Nov 2026 111Ivanti Connect Secure: three exploited flaws, and the first fix wasn't enoughAttackers chained three flaws to get root on fully updated Ivanti Connect Secure VPN appliances. All three are now on CISA's list of exploited vulnerabilities. Which versions fix it, what the attackers did, and what to check. Fact check · 31 Oct 2026 8,988Is a global blackout coming on 17 November? What the data saysViral posts warn of a worldwide blackout on 17 November: the power out, the internet down for three months, bank accounts at zero. Where it comes from, why it can't happen that way, what is really planned that day, and the live status of every country. Analysis · 24 Oct 2026 144LaLiga's IP blocks: why half a million websites break in Spain on match daysTo fight pirate football streams, Spain's ISPs block shared IP addresses during LaLiga matches, and hundreds of thousands of unrelated websites go down with them. What OONI found, what we measured, and what you can do before Barcelona – Real Madrid. Security · 21 Oct 2026 993Node.js security release: ten fixes, one that can run codeOn the same day as PHP2Shell, Node.js fixed ten flaws in its 22, 24 and 26 lines, including a Brotli decoder bug that can allow remote code execution and several ways around TLS hostname checks. What is affected and what to do. Retrospective · Iran, February 2026 684Iran's wartime blackout: 88 days cut off from the worldFrom the first strikes on 28 February to 26 May 2026, Iran was almost completely cut off from the internet: 2,093 hours, the longest nationwide shutdown on record. What happened, how it worked and what it cost. Retrospective · West Africa, March 2024 180West Africa lost four undersea cables in one dayA suspected underwater landslide off Côte d'Ivoire broke four cables at once in March 2024. Ghana was in blackout for almost a week, Côte d'Ivoire fell to 1% of normal. Retrospective · Canada, July 2022 176How a maintenance update took down Canada's RogersIn July 2022 one update in Rogers' core network cut mobile, home internet, debit payments and emergency calls for millions of Canadians for most of a day. Retrospective · Tonga, January 2022 161Tonga: the volcano that cut a country offThe 2022 Hunga Tonga eruption shredded the only cable linking Tonga to the world. The country was almost completely offline for five weeks. Retrospective · Worldwide, October 2021 225The six hours Facebook disappeared from the internetIn October 2021 one routine command took Facebook, Instagram and WhatsApp off the internet for billions of people. No attack, no country outage. Retrospective · Myanmar, February 2021 173Myanmar 2021: a coup, and an internet curfewAfter the February 2021 coup, Myanmar's military cut the internet nationwide, then every night, then all mobile data: a shutdown shaped by the hour. Retrospective · Tigray, Ethiopia, November 2020 170Tigray: two years without a connectionFrom November 2020, the war in Ethiopia's Tigray region came with a phone and internet blackout that lasted about two years. Retrospective · Iran, November 2019 171Iran, November 2019: a country offline for a weekDuring the 2019 fuel protests Iran cut itself off from the internet almost completely, while keeping parts of its domestic network running. Retrospective · Jammu and Kashmir, India, August 2019 166Kashmir: 550 days without full internetThe shutdown that began in August 2019 became the longest ever imposed in a democracy. High-speed mobile internet only returned in February 2021. Retrospective · Egypt, January 2011 163Egypt 2011: the night a country switched off its internetIn January 2011, two days into mass protests, Egypt withdrew almost all its routes from the internet within minutes. It stayed dark for five days. Retrospective · Pakistan, February 2008 196The day Pakistan took YouTube offline for the whole worldIn 2008 a national block on YouTube leaked into the internet's routing system and made the site unreachable worldwide for about two hours.