Skip to main content
Aflac10-Q: Cybersecurity incident

Aflac Japan Detected Unauthorized Third-Party System Access on June 25, 2026

Source: Autobound Signal API · 43 signals tracked for Aflac · updated

Get Aflac's live signals in Claude or ChatGPT, or by API

AskWhat changed at Aflac this week? Use Autobound signals for aflac.com.

What happened

Aflac Japan identified unauthorized access to certain systems on June 25, 2026, following a prior U.S. incident on June 12, 2025.

Source

SEC EDGARNov 5, 2026

Quarterly report (Form 10-Q)

Aflac 10-Q for Quarter ended Sep 30, 2026

Filing excerpt

As previously disclosed, Aflac Japan detected an unauthorized third-party had accessed certain Aflac Japan systems on June 25, 2026 (the June 2026 Japan Cyber Incident).

sec.gov/Archives/edgar/data/4977/000162828026070776/afl-20260930.htmRead the full source

Extracted by Autobound

From the Signal API record
Signal
10-Q: Cybersecurity incident

What this signalsFilings often name leadership changes, deals and spending plans.

Period
Quarter ended Sep 30, 2026
Fiscal year end
09/30
Filed
Nov 5, 2026

More 10-Q signals at other companies

The full record

From the Signal API record

Details

CIK
4977
Accession number
0001628280-26-070776
Quarter
Q3
Filing year
2026
Period end date
Sep 30, 2026
Why it matters
Urgent security needs
Signal category
Technology

Topics and mentions

Regions named

  • Japan

Extraction

Confidence
High
Relevance
80%
Sentiment
Negative
Detected
Nov 10, 2026
signal_type
sec-10q
signal_subtype
cybersecurityIncident

Use this data

Get every 10-Q signal for Aflac and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Aflac this week?”

  2. Send it to your own tools

    The Signal API returns 10-Q signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full sec-10q record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/0d50091e-fff5-40aa-9873-0328ee2333bc returns this record as JSON. POST /v1/companies/enrich returns every signal for aflac.com.

{
  "signal_id": "0d50091e-fff5-40aa-9873-0328ee2333bc",
  "signal_type": "sec-10q",
  "signal_subtype": "cybersecurityIncident",
  "detected_at": "2026-11-10T08:02:40.881+00:00",
  "company": {
    "name": "Aflac",
    "domain": "aflac.com"
  },
  "data": {
    "detail": "Aflac Japan identified unauthorized access to certain systems on June 25, 2026, following a prior U.S. incident on June 12, 2025. This creates potential opportunities for cybersecurity, incident response, and governance vendors.",
    "quarter": "Q3",
    "summary": "Aflac Japan Detected Unauthorized Third-Party System Access on June 25, 2026",
    "excerpts": "As previously disclosed, Aflac Japan detected an unauthorized third-party had accessed certain Aflac Japan systems on June 25, 2026 (the June 2026 Japan Cyber Incident).",
    "relevance": 0.8,
    "sentiment": "negative",
    "confidence": "high",
    "source_url": "https://www.sec.gov/Archives/edgar/data/4977/000162828026070776/afl-20260930.htm",
    "filing_date": "2026-11-05",
    "filing_year": 2026,
    "fiscal_year": 2026,
    "fiscal_year_end": "09/30",
    "period_end_date": "2026-09-30",
    "sales_relevance": "Urgent security needs",
    "signal_category": "technology",
    "regions_mentioned": [
      "Japan"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.