Incident Types: The types of cybersecurity incidents that have occurred include Breach.

Detection and Response: The company detects and responds to cybersecurity incidents through an third party assistance with hudson rock (threat intelligence firm), and containment measures with invalidated active sessions, forced re-authentication, and remediation measures with implemented captcha protections, mandatory two-factor authentication (2fa) for all accounts, and containment measures with mandatory captcha verification, two-factor authentication (2fa) for all future logins, and communication strategy with public statement denying large-scale breach, confirming limited credential stuffing attack..

Common Attack Types: The most common types of attacks the company has faced is Breach.

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through Reused credentials from info-stealing malware infections.

Commonly Compromised Data Types: The types of data most commonly compromised in incidents are Order Histories, Physical Addresses, Full Names, Phone Numbers, Ip Addresses, Product Wishlists, Customer Support Messages, National Id Numbers, Email Addresses, , Names, Postal Addresses, Ip Addresses, Phone Numbers, Product Wishlists, Zendesk Customer Support Messages and .

Third-Party Assistance: The company involves third-party assistance in incident response through Hudson Rock (threat intelligence firm).

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: Implemented CAPTCHA protections, mandatory two-factor authentication (2FA) for all accounts.

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through by invalidated active sessions, forced re-authentication, mandatory captcha verification and two-factor authentication (2fa) for all future logins.

Key Lessons Learned: The key lessons learned from past incidents are Importance of enforcing multi-factor authentication (2FA) and monitoring for credential reuse from previous breaches.

Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: Enforce 2FA for all accounts, implement CAPTCHA protections, monitor for credential stuffing attacks, and educate users on password hygiene. and Implement CAPTCHA and 2FA to prevent credential stuffing attacks.

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at and Source: Threat actor post on hacker forums, and Source: Hudson Rock (threat intelligence firm), and Source: BleepingComputer.

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through Public statement denying large-scale breach and confirming limited credential stuffing attack.

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: were Forced re-authentication with 2FA enabled, CAPTCHA protections implemented., Public statement denying large-scale breach and confirming limited credential stuffing attack.

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as Hudson Rock (threat intelligence firm).

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: Mandatory 2FA, CAPTCHA protections, session invalidation, and forced re-authentication, Mandatory CAPTCHA and 2FA implementation.

Last Attacking Group: The attacking group in the last incident were an daghetiaw and daghetiaw.

Most Significant Data Compromised: The most significant data compromised in an incident were Order histories, physical addresses, full names, phone numbers, IP addresses, product wishlists, customer support messages, national ID numbers, email addresses, Names, postal addresses, IP addresses, phone numbers, product wishlists and Zendesk customer support messages.

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was Hudson Rock (threat intelligence firm).

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were Invalidated active sessions, forced re-authentication, Mandatory CAPTCHA verification and two-factor authentication (2FA) for all future logins.

Most Sensitive Data Compromised: The most sensitive data compromised in a breach were Names, postal addresses, IP addresses, phone numbers, product wishlists, Zendesk customer support messages, Order histories, physical addresses, full names, phone numbers, IP addresses, product wishlists, customer support messages, national ID numbers and email addresses.

Number of Records Exposed in Most Significant Breach: The number of records exposed in the most significant breach was 33.6M.

Most Significant Lesson Learned: The most significant lesson learned from past incidents was Importance of enforcing multi-factor authentication (2FA) and monitoring for credential reuse from previous breaches.

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was Enforce 2FA for all accounts, implement CAPTCHA protections, monitor for credential stuffing attacks, and educate users on password hygiene. and Implement CAPTCHA and 2FA to prevent credential stuffing attacks.

Most Recent Source: The most recent source of information about an incident are BleepingComputer, Threat actor post on hacker forums and Hudson Rock (threat intelligence firm).

Current Status of Most Recent Investigation: The current status of the most recent investigation is Ongoing.

Most Recent Customer Advisory: The most recent customer advisory issued were an Forced re-authentication with 2FA enabled, CAPTCHA protections implemented., Public statement denying large-scale breach and confirming limited credential stuffing attack.

Most Recent Entry Point: The most recent entry point used by an initial access broker was an Reused credentials from info-stealing malware infections.

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was Lack of 2FA enforcement, credential reuse from previous breaches, info-stealing malware infections dating back to 2020, Use of leaked credentials from other breaches.

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was Mandatory 2FA, CAPTCHA protections, session invalidation, and forced re-authentication, Mandatory CAPTCHA and 2FA implementation.