DisclosureLens
GLOBALMalwareAgriculture & FoodAgricultureRansomwareCactusRansom DemandedActor NamedMedium

Sunrise Soya Foods

bd_432ae87e8f151d5f · schema v1 · pii pii-v1

Severity

Medium

Discovered

Filed

Jan 21, 2025

To disclose

Affected

Not disclosed

Confidence

50%
Full breach record for Sunrise Soya Foods

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: Agriculture and Food ProductionDiscovered: 2025-01-30
Listing address (not linked): https://cactusbloguuodvqjmnzlwetjlpj6aggc6iocwhuupb47laukux7ckid.onion/posts/SUNRISE

Source: Ransomware.live

Post text · scraped from the leak site

<p>Grocery Retail.<br><br>“Since 1956, families have trusted Sunrise Soya Foods to provide the best quality tofu to serve at the dinner table. From the first block of tofu to becoming the largest manufacturer in Canada, Sunrise has evolved the tofu market. Making nutritious soy products is our passion and it’s our way of honouring timeless traditions — past, present and future.”<br><br>Website: <a href="https://sunrise-soya.com/">https://sunrise-soya.com/<\/a><br><br>Revenue : $42.2M<br><br>Address: 729 Powell St, Vancouver, British Columbia, V6A 1H5, Canada<br><br>Phone Number: ([REDACTED-PHONE]<br><br><mark class="marker-yellow"><strong>Download link #1:<\/strong><\/mark> &nbsp;<a href="https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/SUNRISE/PROOF/">https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/SUNRISE/PROOF/<\/a><br><br><mark class="marker-yellow"><strong>Mirror:<\/strong><\/mark> <a href="https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/SUNRISE/PROOF/">https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/SUNRISE/PROOF/<\/a><br><br><mark class="marker-yellow"><strong>DATA DESCRIPTIONS:<\/strong><\/mark> Personal identifiable information, database backups, corporate confidential docs, agreements, employees/executives personal files, financial data, HR dept docs, engineering\QA data, corporate correspondence etc.<\/p><p><img src="/uploads/Vancouver_Master_Phone_Extension_April_06_2023_094a81a507.png" alt="Vancouver Master Phone Extension - April 06,2023.png"><img src="/uploads/scan_passport_CA_7faa71b2ea.png" alt="scan passport CA.png"><img src="/uploads/driver_licence_36cf7bbfc5.png" alt="driver licence.png"><img src="/uploads/Denis_Starokha_Criminal_Background_Check_August_18_2022_fd098af641.png" alt="Denis Starokha - Criminal Background Check August 18 2022.png"><img src="/uploads

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jan 21, 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 →