MalwareProfessional ServicesProfessional ServicesRansomwareRansom DemandedRansom PaidData EncryptedTargetedIdentity (basic)Government IDMediumContained

Applied Ecological Services

bd_73d45cebcbce1583 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jun 17, 2019

Filed

Jun 12, 2019

To disclose

—

Affected

497state residents only

Linked

3 filings

Confidence

66%

Full breach record for Applied Ecological Services →

Applied Ecological Services, Inc. notified Montana AG of a ransomware attack on June 17, 2019. The incident affected 497 current and former employees and vendors. Personal information including names, addresses, driver's license numbers, dates of birth, and SSNs was compromised. AES paid the ransom on June 18, 2019, and engaged IT security specialists and law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline — partial

? — ?

Breach window unknown

Jun 12, 2019

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_99847611c91291622019-07-15 · +33dVerified
Oregon State AGbd_782af7451178a1182019-07-17 · +35dVerified

Name: Applied Ecological Services
norm: applied ecological
Domain: appliedeco.com

Name: Applied Ecological Services
norm: applied ecological
Domain: appliedeco.com
Industry: Professional Servicesllm

Discovered: Jun 17, 2019
Breach occurred: Jun 17, 2019
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jul 12, 2019
Affected individuals: 497state-resident count only
Data types: Identity (basic)Government ID
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1189 Drive-by CompromiseT1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Working with law enforcement to look into this incident

During the incident: Consulted with IT security specialists
Paid the ransom
Regained full control of the server
Reviewed the information on the servers subject to the attack
Working with a cybersecurity firm to review its data security
Auditing AES’ current IT security
Working with law enforcement to look into this incident
Changes made: Implementing suggestions for improvement from cybersecurity firm
Auditing current IT security to determine ways in which it can be improved
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.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Montana State AGJun 12 · first · this page

Massachusetts State AG+33d

Oregon State AG+35d

Pattern: first filing Jun 12 (MT), last Jul 17 (OR) — a 35-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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://dojmt.gov/wp-content/uploads/OCP/Breach-NotificationDetails-29.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 12, 2019
Raw hash: fab55b980e589e103b1ccee752769b89f19a68de0ee2475a2e9ff61a6903c295

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityApplied Ecological Services

Victim entityApplied Ecological Services

Incidentdiscovered Jun 17, 2019

Stated responseConsulted with IT security specialists

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov