DisclosureLens
GLOBALUnknownRansomwareAkiraLow

Fiskars Group

bd_60af196b5a289447 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Apr 26, 2024

To disclose

—

Affected

Not disclosed

Linked

8 records

Confidence

60%
Full breach record for Fiskars Group →

Press / market disclosure — not a breach-notification filing

A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.

Data Breach Notification. Fiskars Group: On April 26, 2024, Fiskars Group discovered unauthorized activity on its network that occurred between March 31 and April 8, 2024, during which an actor obtained files containing personal information. The review completed on October 15, 2024 determined that affected individuals’ names and Social Security numbers were exposed. Fiskars engaged cybersecurity experts, notified law enforcement, enhanced its security measures, and is offering affected individuals complimentary 24-month membership in Experian IdentityWorks for identity protection. The cyberattack was claimed by akira on 2024-05-14. Linked ransomware group: akira.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Apr 26, 2024

Press report

—

Corroborated · see linked filings

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

Attack → press

—

Compliance clock

Not assessable

This press report is one of 8 records about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (6) · sorted by filing gap

Show 2 more filings ↓up to 194d gap

Filing propagation · 6 filings · 6 states

View merged incident ↗
Montana State AGNov 6 · first
Oregon State AGNov 6 · first
Maine State AGNov 6 · first
Vermont State AGNov 6 · first
Indiana State AGNov 6 · first

Evidence ladder

Leak-site claim

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

Press / market reportThis record

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

  • incident type + narrative only (may be machine-translated)
  • discovery date
  • materiality
  • affected count
  • 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,856 tracked hereFull profile →