MalwareFinancial ServicesFinanceRansomwareData EncryptedData ExfiltratedCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDFinancial accountMediumContained

MISSION BANK

bd_da9bab8d62b6357f · schema v1 · pii pii-v1

Severity

Medium

Discovered

Dec 2, 2024

Filed

Nov 13, 2025

To disclose

—

Affected

5state residents only

Confidence

67%

Full breach record for MISSION BANK →2 incidents on file

Mission Bancorp experienced a ransomware attack on December 2, 2024, resulting in encryption of systems and potential unauthorized acquisition of files. The incident potentially affected 5 Maryland residents, exposing identity information (SSN, DOB, driver's license, passport) and financial account numbers. Core banking systems were not affected. The company contained the incident, engaged forensic investigators, and offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

Dec 2, 2024

Discovered

Nov 13, 2025

Filed

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed5 affectedView incident

Name: Mission Bancorp
norm: mission bancorp

Name: MISSION BANK
norm: mission bank
Domain: missionbank.bank
Industry: Financial Servicesllm

Discovered: Dec 2, 2024
Materiality determined: —
Notification sent: Jan 6, 2025
Affected individuals: 5state-resident count only
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security numberDate of birth
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified Maryland Attorney General

During the incident: Immediately took steps to secure its network and contain the incident
Engaged a specialized third-party forensic incident response firm
Notified law enforcement
Isolated the impacted systems
Changes made: Changed passwords
Strengthened password requirements
Implemented multi-factor authentication
Reviewing technical safeguards and looking into enhancements to prevent a similar incident
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.maryland.gov/resources-info/SBN%20Documents/2025/ITU-376230.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 13, 2025
Raw hash: a3f621a8e358b09ae2f154e1d46d59c7a2445ae421a1a0440f71db46eda355fd

Reporting entityMission Bancorp

Victim entityMISSION BANK

Incidentdiscovered Dec 2, 2024

Stated responseImmediately took steps to secure its network and contain the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.maryland.gov