Medium severity

Ipsos investigates breach of an internal system, says operations unaffected

The French market research company went public on 16 November, five days after filing a complaint with authorities, but has not said what was accessed.

By Mr Elite Published 6 min read

Severity
Medium
Status
Reported by outlets
Sources
1
Last checked

The short version

  • Ipsos disclosed on Monday 16 November that a breach hit one of its internal information systems, SecurityWeek reported.
  • The company filed a complaint with authorities five days before going public.
  • Ipsos says operations and client delivery were not affected, and that the investigation is ongoing.
  • It has not said whether data was accessed or stolen, which system was hit, or how the intruders got in.
  • No known cybercrime group has claimed an attack on Ipsos, according to SecurityWeek.

What happened

French market research company Ipsos said on Monday 16 November that a breach had hit one of its internal information systems, SecurityWeek reported on 17 November. The company had filed a complaint with authorities five days before the announcement.

Ipsos said it launched its response process after detecting the incident and worked to contain it. It brought in outside security experts to help with the investigation. In its statement it said "The investigation is ongoing" to establish the nature and scope of the incident.

The company said the breach has not disrupted its business. According to SecurityWeek, Ipsos told clients its ability to deliver was unaffected.

Much is missing from the disclosure. Ipsos has not said when it detected the breach, which system was affected or how the intrusion happened. It has also not said whether any data was accessed or stolen, and it declined further comment while the probe continues.

SecurityWeek reported that no known cybercrime group appears to have taken credit for an attack on Ipsos. Ipsos said that if the investigation shows information on clients, projects or business partners was affected, it will contact those concerned directly.

Why it happened

Ipsos has not disclosed a cause. The company has described the event as a breach of an internal information system and nothing more specific, and SecurityWeek said the method of intrusion is unknown.

Without a named system, entry point or date of detection, it is not possible to say whether this was stolen credentials, a software flaw, a mistake by a supplier or something else. Any claim about the cause at this stage would be speculation.

What the company has confirmed is the response: detection, containment, outside experts and a complaint filed with authorities. Ipsos has said it will contact affected clients directly if their information turns out to be involved.

How this kind of failure works

When a company says an internal system was breached, it usually means someone who should not have had access got into a service used by staff rather than a public website. Common routes include a stolen or guessed password, an unpatched server reachable from the internet, or access obtained through a third-party supplier. Which one applies only becomes clear after forensic work.

Investigators begin by reading logs, the records that show who logged in, from where and what they touched. Picture a block of flats with a door-entry system. After a break-in, the first job is to check which key fob opened which door and when, then work out whether the intruder reached a flat or only the lobby. Companies do the same with accounts and servers.

That work takes time, which is why early statements are often thin. Saying whether data was taken depends on evidence of files being copied or sent out, and that evidence can be incomplete if logs are short or were altered. Firms often say the scope is still being determined until the logs have been fully reviewed.

A statement that operations were not affected describes availability, meaning whether systems kept running. It says nothing on its own about confidentiality, meaning whether someone read or copied information. Both questions need separate answers.

Who is affected

It is not yet known who is affected. Ipsos says it has about 20,000 employees across 90 markets and works with 5,000 clients, according to SecurityWeek, but it has not said that any of those people or organisations were involved.

Its services rely on data the company collects itself, including from surveys and social media monitoring. Whether any such data sat on the affected system has not been stated.

If you are an Ipsos client, survey participant or business partner, the company has said it will contact those concerned directly if the investigation finds their information was affected. Until then there is nothing confirmed to act on, though staying alert to unexpected emails that mention Ipsos is sensible.

How to defend against it

Tick each step as you check it. Your progress is saved on this device.

What to learn from this

The concept: Availability versus confidentiality in incident statements

Security people describe harm in three parts: whether systems keep working (availability), whether information stays private (confidentiality) and whether it stays accurate (integrity). A breach can damage one without touching the others. Ipsos has addressed the first and left the second open.

Read an incident statement by asking which of these it covers. No impact on operations is good news about availability, but data theft often causes no outage at all, because copying files does not stop anyone working.

The same distinction appears in ransomware, where availability is the target, and in quiet espionage, where only confidentiality is. Wait for the second part of the answer before judging how serious a breach is.

A company saying its operations were unaffected tells you the systems kept running, not whether anyone read or copied its data.

Quick check

Sign in to earn 10 XP for a right answer

Ipsos says the breach did not disrupt operations. What does that tell you about whether data was stolen?

Timeline

  1. Not disclosed Ipsos detected the incident and began its response process; the date has not been given.
  2. Five days before 16 November Ipsos filed a complaint with authorities, according to SecurityWeek.
  3. Monday 16 November 2026 Ipsos made the breach of an internal information system public.
  4. 17 November 2026 SecurityWeek reported the disclosure and noted no group had claimed responsibility.

What is not known yet

  • When Ipsos detected the breach and how long the intruders had access.
  • Which internal system was affected and how the intrusion happened.
  • Whether any data was accessed or stolen, and whether it concerns clients, projects or partners.
  • Whether any group will claim the attack or any data will appear for sale.

Questions people ask

Has Ipsos confirmed that data was stolen?

No. Ipsos has said the investigation is ongoing to determine the nature and scope of the incident. It has not said whether any data was accessed or stolen. It has promised to contact clients, partners or others directly if their information is found to be affected.

Did the Ipsos breach disrupt its services?

Ipsos says it did not. The company said the incident had no impact on its operations or its ability to deliver for clients. That statement covers service availability and does not answer whether information was exposed.

Who is behind the Ipsos breach?

This is unknown. SecurityWeek reported that no known cybercrime group appears to have taken credit for an attack on Ipsos. Ipsos has not named a culprit or described the method of intrusion, so any attribution would be speculation.

What should Ipsos clients do now?

There is no confirmed instruction beyond waiting for direct contact from Ipsos if their information is affected. Clients can review what data they share with the company and be cautious with unexpected emails about the incident. Verify any such message through known contact channels.

Sources

  • SecurityWeek: Market Research Giant Ipsos Investigating Breach of Internal System 

Know someone who should see this?

Keep reading