JETPLAIN / HISTORICAL RESEARCHACCESSION HIST-012

THE HISTORIC HACK FILES

NotPetya: one patch did not close every route

PERIODJune 2017; later legal record 2020

EDITIONShort field file

AUTHOR REVIEW2026-11-20

An independently written Jetplain dossier · not a government document

The short version

The June 2017 outbreak commonly called NotPetya combined destructive effects with several ways to move through a network. A useful investigation separates initial delivery, movement between computers, and the damage that followed.

An updater in the evidence

Microsoft reported telemetry showing some infections beginning through the legitimate M.E.Doc accounting-software updater. That supported a supply-chain route for observed infections; it did not reconstruct the arrival of the malware at every affected organisation.

More than an unpatched computer

Microsoft described credential theft or reuse of active sessions, file shares, and remote execution through legitimate administration tools. It also documented SMB exploits addressed by MS17-010.

Applying that update closed the particular exploit route. It did not, by itself, explain or prevent movement using valid credentials and administrative access. These methods had different prerequisites; they were not one compulsory sequence on every machine.

The later record has a different job

In its October 19, 2020 announcement, the US Department of Justice described NotPetya as destructive malware and alleged worldwide attacks affecting hospitals and businesses. That announcement concerns an indictment. It expressly states that charges are accusations and defendants are presumed innocent unless proven guilty. It is not a substitute for a final judgment.

From the workbench

Ask which route a safeguard actually closes. A patched service and a reusable administrator credential are different questions. Naming that difference is more useful than treating every infection as proof that somebody simply forgot an update.

What this file leaves open

This short edition does not settle individual criminal responsibility, provide a global damage total, or reconstruct every victim’s recovery. The technical account and the later prosecution announcement answer different questions. Neither is presented as a current removal guide.

Source register

Browse Historic Hacks