Ransomware Tracker by ExposureDrift
Dashboard / Victims / Bugnard

Bugnard was listed on 29 September 2025 by the akira ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). akira listed 54 organizations that month and 1678 in total.

  • Listed 416 days ago.
  • 621 organizations were listed by all groups in September 2025, see the month.
  • 94 in Technology that month.
  • 7 in CH that month.

Updated 2026-11-19 06:00 UTC. Data: public leak-site listings. How we work.

Bugnard corporate emblem
Listed by akira Disclosed: 2025-09-30 11:45 UTC

Bugnard

bugnard.ch Technology CH

Threat Group Post & Evidence

Listed by
Akira 1,678 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

Bugnard is a Swiss market leader for equipment used in the instal lation of electrical and telecommunication networks. We are going to upload 32gb of their corporate data. Financial do cuments, agreements, confidential files, projects, clients inform ation, and lost of other files.

Amounts as written

  • 32gb

Kinds of data mentioned

  • Customer or client data

    “…data. Financial do cuments, agreements, confidential files, projects, clients inform ation, and lost of other files.”

  • Contracts and legal files

    “…are going to upload 32gb of their corporate data. Financial do cuments, agreements, confidential files, projects, clients inform ation, and lost of other files.”

Plain-English summary AI-written

The group says it holds 32 GB of Bugnard corporate data, including financial documents, agreements, confidential files, project and client information, and other files.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with Bugnard (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask Bugnard directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what Bugnard can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data.

Within 30 days

  • Keep watching Bugnard A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Bugnard

First 24 hours

  • Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.

Within 3 days

  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 32gb. Treat group figures as unverified.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
  • Check the ways akira is reported to get in Check these first; they are how the group is reported to work in general.
    • Likely ways in include exploiting SonicWall CVE-2024-40766, stolen VPN credentials, password spraying and flaws in Veeam Backup & Replication. (update of 13 Nov 2025)
    Source: #StopRansomware: Akira Ransomware (AA24-109A) Why: From the public advisory below. It describes the group, not how Bugnard was entered.

Within 30 days

  • Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
  • Check shared suppliers and software List the suppliers and software you share with other Technology organizations and ask them whether they were affected. Why: akira listed 13 other Technology organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain bugnard.ch
Industry Vertical Technology
Country CH
Enrichment Status ENRICHED

Listing severity score (heuristic)

79/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Technology and communications
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
82/100 • CRITICAL
Last Audited: 2026-11-14 17:29 UTC Passive Recon
Total Network Assets 17
6 hosts • 11 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 6
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 1 Staging/Dev
SaaS Ecosystem 1 Cloud Apps
Primary CSP Bugnard SA
Email Security Grade A+ (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Custom Mail Gateway (com)
DNS Authority Authoritative DNS (ch)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by akira

All →
Bench Equity
Financial Services 2026-11-18 15:10 UTC
Audiotec
Technology 2026-11-18 15:10 UTC
Flagship Cruises & Events
Hospitality 2026-11-18 14:11 UTC
Optimil Machinery
Manufacturing 2026-11-17 13:40 UTC
The Mandrel Group
Manufacturing 2026-11-16 13:25 UTC
Galorath
Professional Services 2026-11-13 14:19 UTC