What happened?
In February 2014, Connecticut based Spirol Fastening Solutions suffered a data breach that exposed over 70,000 customer records . The attack was allegedly mounted by exploiting a SQL injection vulnerability which yielded data from Spirol’s CRM system ranging from customers’ names, companies, contact information and over 55,000 unique email addresses.
When did it happen?
The breach date in the public record is February 22, 2014. The record was added to the catalogue on February 22, 2014 and last updated there on February 22, 2014.
What information was reported as exposed?
- Email addresses
- Employers
- Job titles
- Names
- Phone numbers
- Physical addresses
These are incident-level categories. The record does not prove that every category was exposed for every affected person.
Who may be affected?
This record may be relevant to people who had an account or other relationship with Spirol or used spirol.com around February 22, 2014. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.
What should you do?
Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.
Review your credit reports and consider a free credit freeze if identity information could support new-account fraud.
Treat unexpected breach follow-ups with caution. Do not use links or phone numbers in a suspicious message; contact the organization directly.
Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.
Sources and review information
- Have I Been Pwned breach catalogue record ↗
- Federal Trade Commission: What To Do After a Data Breach ↗
- Federal Trade Commission: Credit Freezes and Fraud Alerts ↗
Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.