St. Paul Center for Biblical Theology
bd_052fed53e72f2142 · schema v1 · pii pii-v1
Full breach record for St. Paul Center for Biblical Theology →St. Paul Center for Biblical Theology experienced a data security incident involving malware installed in its online purchasing software. The malware allowed unauthorized scraping of payment card data (including CVV, PIN, or expiration date) from customers who made purchases or donations between March 3, 2020, and August 9, 2020. The incident was discovered on August 20, 2020, after notification from a payment processing vendor. The organization contained the malware, audited systems, and implemented stricter vulnerability identification processes.
J jump to incidentP pin to compareR raw source
Incident timeline
Mar 3, 2020
Begins
Aug 20, 2020
Discovered
Oct 2, 2020
Filed
vs. sector median
2 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Montana State AGbd_4e9e7466b1331e622020-10-02Candidate
- New Hampshire State AGbd_329a6cd45c41ba072020-10-05 · +3dVerified
- Massachusetts State AGbd_fa94e04ca322d6412020-10-07 · +5dVerified
- Maine State AGbd_2e319855b6bc87082020-09-24 · +8dCandidate
Show 2 more filings ↓Show fewer ↑up to 14d gap
- Indiana State AGbd_a4693205a7b69b272020-09-24 · +8dVerified
- Maine State AGbd_bafaa2c1b73e83a42020-09-18 · +14dCandidate
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Sep 18 (ME), last Oct 7 (MA) — a 19-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.