Five years ago today, Diamond Comic Distributors was struck by ransomware. Hackers associated with the Conti group infiltrated Diamond’s system and brought it down for almost a month.

November 5th was a Friday. On Wednesday, we sent PREVIEWS #399 to press. On Thursday, we sent the US order forms to press. On Friday…
I arrived at the office to work on the UK order form. I expected an email from our UK team, I would perform Excel and Word alchemy, I would send Casey some files, and I’d call it a day in the early afternoon when everything was done.
Diamond went remote in March 2020, and despite an RTO mandate in late 2020, it remained remote. I worked more of a hybrid schedule; working days in the office when I needed office resources (like the printers), performing delicate tasks that I didn’t trust to a remote connection, or just a change of scenery. The weeks when the catalog closed and everything went to press, I’d be in the office five days, occasionally four (sometimes working remotely on Monday).
Stepping off the elevator on Friday, I was greeted by a handwritten sign: “Computers are down until further notice.” I left a box of dounts in Graphics — it was National Donut Day, and I knew there would be a few people in the office, even on a Friday — and went to my office. Someone, probably IT, knowing that I was a frequent office user, left a note on my computer telling me not to touch it, and I didn’t. I turned on my monitor, looked at my Windows lock screen wallpaper (an image of the interior of the Natioal Cathedral), and tried to occupy myself while I wanted.

I Marie Kondo-ed my office.
I threw out old paperwork and junk.
I organized my desk.
I cleaned out the desk drawers.
I built an off-brand LEGO set of the space shuttle.

It was still only about noon.
Cindy Anderson, Diamond’s production manager, was also in the office that day. She too was cleaning out her office, and she stopped by my office to show me Quebecor invoices from 2001 that she had held onto through three, maybe even four, different buildings.
“The computers,” she said. “I bet it’s ransomware.”
“Well, that would suck,” I said.
By 12:30 I said to myself, “This day is done.” The UK order form, which was no longer printed, just a PDF, could could wait until Monday. I left, went to Baja Fresh for lunch, and headed home.
We had a Teams call in Marketing on Tuesday, and that was when we learned that, yes, it was ransomware and top people were looking into it. Top… people.
On the PREVIEWS team, some of us started talking about how we would do PREVIEWS #400 without any of our tools–no PID, no InDesign templates, nothing.
I was going to need a tool.
Specifically, I was going to need a tool that would take an unstructured and raw Microsoft Word document and structure it in a way that an InDesign template would read and understand. (PID, the usual PREVIEWS tool, did this automatically. We needed something for the case where it would not be automatic.) Elena developed new InDesign templates, we hashed out the style names she would use, and I began coding a Microsoft Word macro.
The good thing was we had the quarterly week break between catalogs, so I had time. I also had some of the raw Word documents that PID produced at home. All I had to do was to take one of those Word documents and structure it with Styles.
The macro is dated November 14th, nine days after the ransomware attack, though it developed over several days.
It is not elegant. My comments in the VBA call it a “sledgehammer.” After it was run, to the naked eye, it appeared that nothing had changed; the text on the screen appeared to be exactly as it had been. But under the hood, the Word document had structure.
We hit the publishing deadline on PREVIEWS #400. No remote access, just a backup network in the office that was walled off from the infected servers and the tools that Elena and I built separately to get it done.
Oh, and I had COVID. Despite every precaution I took, I picked it up at the Maryland Irish Festival. The over symptoms were mild, just loss of taste and smell for a day, but the fatigue after lasted until late spring.

There was a problem. I worked the problem. The tools I built I applied to other projects, like the PREVIEWS UK Supplement, until my end with Diamond four years later.
I never felt like I’d done anything special. I did what I needed to do.
People have asked me in interviews how I dealt with a crisis at work. This is the story I tell.