Welcome to The Calibre Brief, a Calibre Code USA production.

Two weeks after an AI-assisted attack exposed South Korea’s banking side doors, the urgent question is simple: what changed, and who can prove it?

On September 28, Shinhan’s loan-agent portal became a side door. Brokers used it to check applications, but attackers queried details from 25,729 people. The intrusion bypassed customer-facing banking, moving through employee and broker systems. Shinhan took about 30 hours to cut the connection; KB Kookmin detected compromise after roughly 43 hours.

ARTEX was not an autonomous hacker. It was an open-source framework that let a human direct a language model through reconnaissance and exploitation, including SQL injection and authentication bypasses. Investigators matched it through attack IPs, server logs, and a traffic signature. Neglected back doors could be found faster than banks found them.

Regulators hold the measurable overhaul. An inspection of 555 companies found deficiencies at 130. Authorities recommended audits and promised large firms twice-yearly assessments. Banks reported breaches and blocked IP addresses, but investigators called blocking “little more than emergency first aid.” No bank has published an after-attack detection time. This absence is not proof of inaction. Why two banks resisted remains interpretation, not proof.

What would verify improvement? Remediation counts for the 130 flagged companies, detection times measured against the old figures, and independent checks of employee-facing portals. For now, the clearest defense evidence comes from Woori and NH NongHyup, whose protections existed before the attack. ARTEX returned commercially within days, faster than public proof of repair.

The lesson is not that nothing changed. It is that the overhaul remains regulator-measured, while banks have not published numbers letting customers verify they are safer.

This is The Calibre Brief from Calibre Code USA. What numbers should breached banks publish so customers can verify improvement? Share your answer in the comments, like and subscribe on YouTube, and follow the podcast.