HackingTechnologyInformationCustomer Data InvolvedCredentialsIdentity (basic)LocationMetadataLowContained

Armor Games Inc.

bd_7d0336bf0bfb373e · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 29, 2019

Filed

Feb 22, 2019

To disclose

24 days

Affected

Not disclosed

Linked

3 filings

Confidence

65%

Full breach record for Armor Games Inc. →

ArmorGames, Inc. disclosed a data breach affecting user accounts, occurring around January 1, 2019, and discovered on January 29, 2019, after notification by Tuik Security Group. The breach exposed usernames, email addresses, IP addresses, hashed passwords, and password salts. The company confirmed the breach was part of a larger incident affecting 16 companies. ArmorGames responded by auditing systems, requiring password updates, hardening security, and notifying authorities. No financial data or physical addresses were involved.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 28 days

discovery → filing · 24 days

Jan 1, 2019

Begins

Jan 29, 2019

Discovered

Feb 22, 2019

Filed

vs. sector median

15 wks faster

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

Oregon State AGbd_ef9064e6040f961c2019-02-25 · +3dVerified
California State AGbd_8327e2094108f8022017-11-21 · +458dCandidate

Name: Armor Games Inc.
norm: armor games
Domain: armorgames.com

Name: Armor Games Inc.
norm: armor games
Domain: armorgames.com
Industry: Technologyllm

Discovered: Jan 29, 2019
Breach occurred: Jan 1, 2019
Undetected for: 28 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: CredentialsIdentity (basic)LocationMetadata
Attack vector: Unknown
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Begun notifying authorities

During the incident: Immediately began an investigation which included an ongoing audit of our hosting provider, web servers, and database systems
Require our users to update their passwords
Making changes on our side to harden our security and fixing any weaknesses found by our audit
Updating our password protection methods
Adding measures to protect our users from misuse of this information on our own site
Begun notifying authorities and will cooperate with law enforcement if requested
Changes made: Updating our password protection methods
Making changes on our side to harden our security and fixing any weaknesses found by our audit
Adding measures to protect our users from misuse of this information on our own site
Continue to look for new ways to minimize our data collection
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 24 days(24 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

California State AGNov 21 · first

California State AG+458d · this page

Oregon State AG+461d

Pattern: first filing Nov 21 (CA), last Feb 25 (OR) — a 461-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://oag.ca.gov/ecrime/databreach/reports/sb24-144941
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 22, 2019
Raw hash: 15da7ce5aa2c6958f9329936c3a1461ec854f5dbe60793655f406422ecffc7cc

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityArmor Games Inc.

Victim entityArmor Games Inc.

Incidentdiscovered Jan 29, 2019

Stated responseImmediately began an investigation which included an ongoing audit of our hosting provider, web servers, and database systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov