DisclosureLens
GLOBALMalwareAgriculture & FoodAgricultureRansomwareAkiraRansom DemandedActor NamedMedium

The McGregor

bd_82e215034ace0726 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

May 3, 2023

To disclose

—

Affected

Not disclosed

Linked

2 records

Confidence

50%
Full breach record for The McGregor →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Akira 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: 2023-05-03

Source: Ransomware.live

Post text · scraped from the leak site

The McGregor company specializes in supplying equipment, and consultation to ensure crops are for growers. This McGregor was unable to an attack and lost 362GB of data. The content the has supplied us will be available here soon. McGregor falls sometimes.

Incident timeline — mostly unverified

? — ?

Breach window unknown

May 3, 2023

Claim posted

—

Corroborated · see linked filings

This record's own dates cannot anchor compliance clocks; see the linked filings.

Claim → filing

—

Compliance clock

Not assessable

This leak-site claim is one of 2 records about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

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 2023-04-12

akira

According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs

1,853 tracked hereFull profile →