Skip to content

Blue Yonder ransomware incident

Summary

Blue Yonder logo

A Nov. 21, 2024, ransomware attack disrupted Blue Yonder’s managed hosted services and affected customers including Starbucks. Service returned in stages, while the company investigated an attacker’s separate data-theft claim.

Key facts

Timeline

  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Impacted location

Organization types

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

    Malware that encrypts systems or data, typically accompanied by a ransom demand.

Data impacts

  • Unknown data impact

    The incident is cyber-related, but available evidence does not establish whether or how data was affected.

Operational impacts

  • Application unavailable

    A specific application or software platform became unavailable or unusable.

  • Cloud service disruption

    Cloud-hosted infrastructure, software, storage, identity, or platform services were unavailable or materially impaired.

  • Records processing disruption

    The organization could not create, update, search, file, approve, transmit, or otherwise process records normally.

  • Scheduling disruption

    Appointment, booking, reservation, dispatch, staffing, or other scheduling functions were unavailable or impaired.

  • Supply chain disruption

    Procurement, inventory, warehousing, shipping, delivery, vendor, or other supply-chain processes were materially affected.

  • Service delay

    Services continued but with longer processing, response, delivery, or completion times.

  • Manual workaround required

    Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.

  • Staff unable to work normally

    Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.

  • Third-party service disruption

    The incident materially affected services delivered by or through a vendor, managed service provider, contractor, partner, or other third party.

  • Downstream organization impact

    The incident caused operational effects at customers, affiliates, subsidiaries, partners, tenants, or other dependent organizations.

Extortion indicators

  • Leak-site listing

    The victim was listed on a threat actor or ransomware data-leak site as an alleged target or nonpaying victim.

Incident narrative

Managed hosted services disrupted

Blue Yonder said a ransomware incident disrupted its managed services hosted environment Nov. 21, 2024. Its original incident updates describe outside cybersecurity assistance, defensive measures and restoration work.

The company initially had no restoration timetable. It said it was monitoring its Azure public-cloud environment and had not seen suspicious activity there at that time. That statement did not establish that every Blue Yonder environment or customer was affected.

Downstream workforce disruption at Starbucks

Starbucks’ employee scheduling and hours-tracking platform was disrupted, requiring manual tracking so employees could be paid. Cybersecurity Dive reported Dec. 12 that Starbucks had confirmed the platform was back in service the previous day.

Starbucks said its Blue Yonder connection had been disconnected, rather than describing direct attacker access to Starbucks systems. It planned continued checks on pay accuracy. The operational disruption does not establish theft of Starbucks employee information or closure of its stores.

Pen maker BIC reported limited shipping delays on Nov. 27. Its spokesperson said the outage did not directly affect its operations. That statement does not establish a BIC factory shutdown.

Recovery remained staged

Blue Yonder’s Dec. 1 update said several affected customers were back online while others were still being restored. By Dec. 12, it said a significant majority had service restored and work with affected customers continued.

These milestones do not identify an exact date when every customer’s service returned. Later archival capture dates also do not extend the duration of an outage described in an earlier update.

Claims and separate investigations

The Record reported Dec. 6 that Termite claimed responsibility and alleged theft of 680 gigabytes. Blue Yonder acknowledged an unauthorized party’s claim and said it was investigating; it did not independently confirm that volume in the reviewed update.

Later Clop claims concerning Cleo file-transfer software are a separate reported matter. Blue Yonder said it had no reason to connect that vulnerability with the November incident. Neither claim establishes a verified ransom payment or personal-information victim count for this outage.

Later business consequences

In an Oct. 30, 2025, investor presentation, Panasonic linked higher Blue Yonder customer churn and slower annual recurring revenue growth to the cyberattack. It described security investments and customer follow-up. These business consequences do not establish that the original service outage continued into 2025.

Current assessment

The incident is presumed resolved because the last directly verified restoration work was documented Dec. 12, 2024. The reviewed sources do not establish an exact end date for all affected customers. Later theft claims and investigations do not extend the documented operational disruption.

Threat actor and claim

Listed as: Blue YonderSource: ransomware.liveDiscovered:

Claim details

Ransomware.live lists Blue Yonder under Termite, discovered Dec. 6, 2024. Contemporary reporting describes the group’s allegation that it stole 680 gigabytes. Blue Yonder acknowledged a third party’s theft claim but did not independently confirm the alleged volume, actor or a ransom payment. Tracker discovery is not the original post time or intrusion date. The separate later Clop/Cleo matter is not assigned to this November incident. Preserve the existing Termite identity and its separately sourced research.

Organizations involved

Impacted location

  • Scottsdale, Arizona

    Medium Confidence

    The company currently identifies 15059 N Scottsdale Rd as its Scottsdale administrative office, while incident-period reporting identified Scottsdale as its headquarters. Preserve the supported existing office-city relationship. Three public Census street-address forms returned no match, so exact municipal jurisdiction is not independently verified; the official map viewport is not treated as an exact office point. No compromised-server location, citywide outage or additional customer geography is inferred.

Sources

Blue Yonder cybersecurity incident updates

Blue Yonder confirmed that ransomware disrupted its managed hosted services on Nov. 21. Customers returned in stages; the Dec. 12 update said a significant majority were restored and work with affected customers continued.

BIC, Starbucks, Morrisons continue recovery after Blue Yonder ransomware attack

A BIC spokesperson reported limited shipping delays and said the Blue Yonder outage did not directly affect BIC’s operations. Starbucks said it processed payroll as planned while staff used manual scheduling workarounds.

Blue Yonder says some customers restored as ransomware gang boasts of attack

The report described staged customer restoration and a Termite claim that it took 680 gigabytes. A Blue Yonder spokesperson discussed recovery but did not confirm the claim or disclose a ransom demand.

Blue Yonder helps restore operations for majority of impacted customers

Starbucks confirmed its employee scheduling platform was back in service by Dec. 11 after manual tracking of hours. It said its Blue Yonder connections had been disconnected, rather than reporting direct attacker access to Starbucks systems.

Blue Yonder says November ransomware attack not connected to Cleo vulnerability

Blue Yonder said it had no reason to connect a Cleo file-transfer vulnerability and later Clop theft claims with its November ransomware incident. It was investigating potential Cleo-related effects separately.

Panasonic Fiscal 2026 second-quarter financial results, Blue Yonder update

Panasonic attributed slower year-over-year growth in Blue Yonder’s software annual recurring revenue to increased customer churn caused by the cyberattack. It described security enhancements, targeted investments and customer follow-up.

Ransomware.live Termite listing for Blue Yonder

A tracker listing identifies Blue Yonder and blueyonder.com under the Termite operation, with discovery recorded Dec. 6, 2024.

See something that needs correction?

Signed-in members can report an error, update, or missing source.