Azure Standard data breach: card-skimming code on the checkout page for a week

Date	Event
August 15, 2026	Skimming code placed on the payment page through a third-party code management platform
August 22, 2026	Company engineers find the code; it is removed within minutes
August 23, 2026	Preliminary email to customers
September 24, 2026	Letters by first-class mail; notice to New Hampshire
September 25, 2026	Report to Massachusetts (267 residents)

What happened at Azure Standard?

It was a web skimming attack, the kind that copies what a shopper types at checkout. The notice says the code copied payment information as customers entered a new payment method and sent a copy to a server the attacker controlled. Legitimate payments kept going through, so the attack caused no obvious interruption.

The way in was not Azure Standard's own servers. The attacker used a third-party code management platform linked to the website, and the company says there was no broader compromise of its customer databases or other systems. The notice does not name the platform.

Was my card affected if it was already saved?

No, according to the company. Only payment methods entered during the week were copied. Methods saved before August 15, 2026 were not affected. The incident did not involve account passwords, Social Security numbers, driver's license numbers or health information.

What information was exposed?

It depends on the payment method. For a card: number, expiration date and security code. For a bank payment: account and routing numbers. The name and billing address entered with the payment were taken too.

Record	People	Data it marks
Azure Standard notice to New Hampshire (September 24, 2026)	3,743 customers nationwide	Card number, expiry and security code; bank account and routing number; name and billing address
Massachusetts OCABR, report 2026-1624 (September 25, 2026)	267	Financial accounts, card numbers

What did Azure Standard do?

The notice lists the clean-up in detail. The company removed the code, disabled the compromised account, changed affected credentials and rebuilt the website from verified clean source code. It also told its payment partners and the card networks, brought in an independent firm, and reported to law enforcement and regulators.

The company emailed customers on August 23, the day after it found the code, before the formal letters. The letters followed 33 days after discovery. The payment card breach notice guide compares other checkout-page attacks.

What is Azure Standard offering?

Twelve months of Experian credit monitoring. Questions go to (971) 200-8350 or accountsupport@azurestandard.com. For a skimmed card, the first step is the one the August email gave: check recent activity and call the card issuer or bank. For how offers compare, see the credit monitoring guide.

What the documents leave open

• Which code management platform was used, and how the attacker got access to it.
• How many of the 3,743 customers paid by card and how many by bank account.
• Whether any copied cards have been used for fraud.