CodeSecure Inc Data Breach Notice (Indiana Attorney General)

The data breach at CodeSecure Inc means that personal information belonging to seven Indiana residents has been exposed. The incident occurred on September 15, 2025, yet the filing was not made until October 28, 2026 — an interval of 408 days.

Personal Information That Cannot Be Replaced

The filing lists personal information as exposed. Because this category can include details such as names, addresses, dates of birth or other biographical data, the records affected do not expire. Once released, this information remains usable for identity fraud or targeted social engineering indefinitely.

No passwords, financial account numbers, Social Security numbers, driver’s license numbers, or other government identifiers appear in the categories named by the record. This is genuinely good news: the breach does not require you to change any CodeSecure password, and the most permanent government identifiers that typically cause the greatest long-term harm are not listed as exposed.

What the 408-Day Gap Changes for You

The long delay between the September 15, 2025 incident and the October 28, 2026 filing is the most notable fact in the record. During that period the organisation investigated the breach and prepared notifications. The filing itself does not disclose when CodeSecure discovered the incident or whether any data was confirmed exfiltrated.

CodeSecure is required to notify affected individuals directly, usually by post. If you have not received a letter, it is likely your information was not among the seven records included. However, if you have moved since September 15, 2025, the letter may have gone to an old address. In that case, contact CodeSecure directly to confirm whether you were affected.

What This Exposure Enables

Personal information alone can still support convincing impersonation attempts, phishing emails that appear tailored to you, or pretexting calls that reference details only CodeSecure should know. Because the record names only this broad category, the precise combination of details each of the seven people received is known only to them through their individual notification letters.

The small number of people affected — just seven — suggests the breach was narrowly scoped, but the 13.4-month gap before notification remains the central fact anyone named in this filing must weigh.

How to Protect Yourself Going Forward

• Monitor your credit reports and accounts for unusual activity. Even without Social Security numbers exposed, personal details can help fraudsters build convincing profiles.
• Treat any unexpected contact claiming to be from CodeSecure with caution. Verify requests independently rather than using details provided in the message.
• Be wary of phishing attempts that reference your relationship with CodeSecure. The exposed personal information can make such attacks more believable.
• Keep your own records of the incident date and the letter you receive. This helps if you later need to dispute fraudulent activity linked to this breach.