DisclosureLens
GLOBALMalwareTransportation & LogisticsTransportationRansomwareAvoslockerRansom DemandedActor NamedMedium

Blume Global, Inc.

bd_817ef0938ce50857 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Dec 26, 2022

To disclose

—

Affected

Not disclosed

Linked

4 filings

Confidence

50%
Full breach record for Blume Global, Inc. →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Avoslocker 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: Transportation/LogisticsDiscovered: 2022-12-26
View aggregator listing on ransomware.liveView merged incident timeline

Source: Ransomware.live

Post text · scraped from the leak site

BLUME GLOBAL INC BLUME GLOBAL INDIA PRIVATE LTD BLUME GLOBAL HONG KONG LIMITED Data Stolen: Proprietary & Confidential, Strictly Confidential NDA agreemtents signed by DocuSign with: J.P. Morgan Securities LLC, Mitsui & Co (mitsui.com) Signatory Mariko Tsuchida(Deputy General Manager), Yara International ASA Signatory Loredana Nistor(IT Sourcing Manager), Dell Inc. Signatory Lisa Woo(Legal Counsel, Legal Strategy and Operations), Hewlett Packard Enterprise Company Signatory Kim Masone(VP Global Logistics Operations), Desarrollo Logístico, S.A., FAIRMOUNT PARTNERS, CITIGROUP GLOBAL MARKETS INC. Signatory Eric Burns(Managing Director), MARLIN MANAGEMENT COMPANY LLC Signatory Ryan Laurin(Managing Director), GI PARTNERS ACQUISITIONS LLC, LiveSource Inc., Röhlig blue-net GmbH, REZ1 Cisco NDA etc + email-bases, private conversations .msg, financial statement etc. We uploaded small size of Stolen data in Blumeglobal_Part1.zip archive.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Dec 26, 2022

Claim posted

—

Corroborated · see linked filings

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

Claim → filing

—

Compliance clock

Not assessable

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

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 2 states

View merged incident ↗
Massachusetts State AGAug 11 · first
Maine State AGAug 11 · first
Leak Site+137d · this page

Pattern: first filing Aug 11 (MA), last Dec 26 — a 137-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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.

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 2021-06-13

avoslocker

According to ransomware.live, AvosLocker is the ransomware payload of the Avos RaaS group, active from July 2021 to approximately May 2023, targeting education, manufacturing, and healthcare sectors on Windows, Linux, and VMware ESXi environments, with the US accounting for ~72% of victims.

70 victims claimed globally70 tracked hereFull profile →