DisclosureLens
GLOBALMalwareRetail & ConsumerRetailRansomwareCactusRansom DemandedActor NamedMedium

rocketstores.com

bd_f74d9efb20f9f1ed · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Feb 26, 2025

To disclose

—

Affected

Not disclosed

Confidence

50%
Full breach record for rocketstores.com →2 incidents on file

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Cactus on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: Consumer ServicesDiscovered: 2025-03-12
Listing address (not linked): https://cactusbloguuodvqjmnzlwetjlpj6aggc6iocwhuupb47laukux7ckid.onion/posts/ROCKETSTORES

Source: Ransomware.live

Post text · scraped from the leak site

<p>Convenience Stores, Gas Stations &amp; Liquor Stores.<\/p><p>“Founded in 1955 and based in Long Beach, California, we are one of the largest independent owners, suppliers and operators of gas stations and convenience stores in the Western United States. We have over 3,500 Team Members in more than 450 locations spread across California, Oregon, Washington and Colorado and we're still growing!”<\/p><p>Website: https://rocketstores.com/<\/p><p>Revenue : $738.9M<\/p><p>Address: 4130 Cover St, Long Beach, California, 90808, United States<\/p><p>Phone Number: ([REDACTED-PHONE]<\/p><p><mark class="marker-yellow"><strong>Download link #1:<\/strong><\/mark> <a href="https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/ROCKETSTORES/PROOF/">https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/ROCKETSTORES/PROOF/<\/a><br><br><mark class="marker-yellow"><strong>Mirror:<\/strong><\/mark> <a href="https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/ROCKETSTORES/PROOF/">https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/ROCKETSTORES/PROOF/<\/a><\/p><p><mark class="marker-yellow"><strong>DATA DESCRIPTIONS:<\/strong><\/mark> Personal identifiable information, corporate internal data, contracts, NDAs, financial data\payroll, legal documents, employees and executives personal data, corporate confidential and personal correspondence, etc.<\/p><p><img src="/uploads/2024_Ryan_Contract_Apro_fully_executed_16ca910a91.png" alt="2024 Ryan Contract Apro fully executed.png"><img src="/uploads/incident_report_3_3_23_9b3e1a0e3e.png" alt="incident report 3-3-23.png"><img src="/uploads/Project_Sunshine_CIP_confidential_do_not_share_or_distribute_77785b7491.png" alt="Project Sunshine_CIP_confidential do not share or distribute.png"><img src="/uploads/2025_02_11_Settlement_Demand_Letter_and_Complaint_usps_2_18_aabf72c3af.png" a

Incident timeline — mostly unverified

? — ?

Breach window unknown

Feb 26, 2025

Claim posted

—

No filing yet · watching

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

Claim → filing

—

Compliance clock

Not assessable

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

Evidence ladder

Leak-site claimThis record

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

Press / market report

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

State AG / regulator filing

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

SEC 8-K / victim statement

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

No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2023-07-03

cactus

According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs

249 tracked hereFull profile →