Cyber & AI intelligence
Briefs indexed3967
Issues37
Published Mondays07:30 CT
▣ Breach POSTE-ITALIANE-POS 2026-11-21

Poste Italiane: PosteCert Breach Exposes Remote Signature Contracts

"Poste Italiane has confirmed that someone got into PosteCert without authorisation. PosteCert is the company's platform for certified email (PEC), digital and electronic signatures, digital archiving and timestamping…"

Poste Italiane has confirmed that someone got into PosteCert without authorisation. PosteCert is the company's platform for certified email (PEC), digital and electronic signatures, digital archiving and timestamping. The confirmation came after a user called flex22 posted an archive of about 1 GB on an underground forum. Italian outlets that examined the files say it holds 2,158 contracts for the Firma Digitale Remota (remote digital signature) service and personal records for 1,561 people. The company says only a limited number of people are affected and that no data about their financial dealings with Poste was taken. No login credentials or payment data have turned up in the archive. The contents are still detailed enough to support targeted phishing and identity fraud against professionals, businesses and public-sector staff, who make up most of PosteCert's users.

What Happened

Reports differ on when the archive first appeared. La Repubblica and TechPost date the forum post to 17 November 2026. Forux puts it on 18 November, which matches the date threat-tracking account Hackmanac gives for its first sighting. Il Post says the intrusion itself happened overnight between Monday 16 and Tuesday 17 November. That fits Corriere della Sera's finding that the newest document in the archive is a registration dated 16 November, the day before flex22 made the claim.

Accounts also differ on how the data is being offered. Forux and TechPost describe the post as an offer to sell. Corriere della Sera and Il Fatto Quotidiano say the documents had been free to download on a dark web forum for at least three days. Il Post says the data was "published online". The data may have been offered for sale and also leaked in part or in full, but no outlet has confirmed which.

Poste Italiane confirmed the breach on the morning of 19 November, according to Corriere della Sera and TechPost. Its statement, quoted the same way across Italian outlets, reads: "Checks on the case are under way. Initial analysis shows the breach concerns a limited number of people, and the information taken does not involve sensitive data relating to their financial dealings with the company." The company stressed that PosteCert was affected and PosteID was not. PosteID is its digital identity service, used to log in through SPID, Italy's public digital identity system. Hackmanac's early alert had named "Postecert/PosteID", and TechPost reports that Poste says PosteID and SPID were not compromised.

The service involved has been described in two ways. Poste's own clarification, as reported by Corriere and Il Fatto, calls PosteCert its certified-email service. The leaked files, though, are contracts for the remote digital signature product, which also runs under the PosteCert brand. Il Post specifically names the PosteCert Firma Digitale Remota archive as the source.

Poste Italiane has not published a formal breach notice. No filing with Italy's data protection authority, the Garante per la protezione dei dati personali, has been made public. Under GDPR the company has 72 hours from becoming aware of the breach to notify the Garante, and it would normally be expected to tell the affected customers directly.

What Was Taken

Corriere della Sera's analysis of the archive gives the clearest breakdown, and the other reports match it:

Each record can contain:

Il Post reports that the archive also includes certificates, orders and invoices, plus the names of the assigned portfolio advisers for almost 650 customers. Italian outlets cite RansomNews, a breach-monitoring site, as saying the victims live in every Italian region, with the most in Lombardy, Lazio and Campania.

Reports disagree on the date range. Corriere della Sera and TechPost say the contracts run from 2020 to 2026. Il Fatto Quotidiano says 2017 to 2026, and Corriere's own detailed analysis also puts the oldest document in 2017. Most of the contracts look recent, and some were signed days before the theft.

According to Il Post, the published material does not include passwords, login credentials, account numbers, payment card numbers, private keys, or the codes used to apply digital signatures. La Repubblica reports no evidence so far of anyone accessing customer accounts or misusing digital signatures.

Why It Matters

The number of victims is small compared with Poste Italiane's customer base. The value of the data to a fraudster is high. These are people who recently bought a legally binding digital signature, and that group is made up mostly of accountants, lawyers, company directors and public-sector staff. One record pairs a verified identity document number and tax code with a contact email, a phone number, the exact product the person bought, and in hundreds of cases the name of their Poste adviser. That is enough to build a convincing pretext.

The likely follow-on attacks include:

Because many victims sign documents for their employers or for public bodies, any identity takeover could reach beyond the individual to contracts, tenders and official filings.

The Attack Technique

No one has said how flex22 got in. Poste Italiane has not released technical details. Forux suggests a vulnerability was probably exploited but gives no evidence. The pattern of a single archive of contract documents and order records suggests the attacker reached a document store or back-office system behind the remote signature service, not individual customer accounts. That has not been confirmed.

There is a separate PosteCert issue defenders should know about. CVE-2026-9661 (also listed as EUVD-2026-125784) was published on 13 November 2026, a few days before the breach. It affects PosteCert FIRMAOK! 1.6.29 on Windows, the desktop signing application. ENISA and Rapid7 describe the flaw the same way. The program's launcher.exe, updater.exe and tslupdater.exe load OpenSSL configuration and library files from a hardcoded directory that does not exist by default and that ordinary users can write to. A low-privileged local user can create that directory and plant malicious files. The application then runs the attacker's code with the privileges of whoever starts it, and if an administrator starts it, that can mean full control of the machine. It scores 7.3 on CVSS 4.0 (7.0 on CVSS 3.1). It is not in the CISA or EU known-exploited catalogues, and EPSS puts the chance of exploitation in the next 30 days at 0.18% (ENISA) or close to 0% (Rapid7).

Nothing links CVE-2026-9661 to this breach. It is a local privilege escalation flaw in client software running on users' own PCs. It would not give remote access to Poste's central contract archive. It is relevant here mainly because organisations that use PosteCert signatures probably have FIRMAOK! installed on their workstations.

What Organizations Should Do

  1. Warn staff who hold PosteCert or Poste remote signature certificates. Tell them to expect convincing phishing, SMS and phone calls that mention their real contract, product or adviser. Tell them to verify contact through official Poste channels and never through links or numbers given in a message.
  2. Patch or harden FIRMAOK! on Windows endpoints. Find installations of version 1.6.29, apply the update from Poste's official download page once one is available, and meanwhile block ordinary users from creating the hardcoded OpenSSL directory. Do not let administrators run the application from privileged sessions.
  3. Tighten approval for anything signed digitally. For high-value documents, payment instructions or changes to bank details that arrive digitally signed, confirm through a second channel. A stolen identity combined with a fraudulently issued certificate would produce a signature that looks valid.
  4. Watch for identity misuse. Affected people, and organisations whose officers are affected, should look out for unexpected SPID, digital signature or credit applications made in their names, and report identity document numbers that may be compromised.
  5. Update email and phone filtering for Poste-themed lures. Add detection rules for PEC, PosteCert and Firma Digitale lures, check sender domains against Poste's real ones, and flag lookalike domains registered after 17 November.
  6. Review your own third-party exposure. If your organisation sends customer identity documents to a signature or trust-service provider, ask how long that provider keeps the documents and how it limits access. Make breach notification timelines part of your contracts.

Sources: Violazione PosteCert: Poste Italiane conferma l’intrusione | EUVD-2026-125784 EUVD | CVE-2026-9661: Uncontrolled Search Path Element Rapid7 Vulnerabili... | Attacco hacker a Poste Italiane: violata la piattaforma per la mail... | A Poste Italiane sono stati rubati i dati anagrafici di oltre 1.500... | PosteCert, rubati i dati di oltre 1.500 clienti. Quali sono i risch... | Violazione dati Poste Italiane: 1.561 clienti esposti sulla darknet | Poste conferma la violazione: un gigabyte di dati in rete, PosteID...