News for hackers. Stuff that matters.
Re:A case study in PDF forensics: The Epstein PDFs by anigbrowl on Wednesday February 04, 2026 @01:10PM (#46889343)
I found this part interesting:

There are also other documents that appear to simulate a scanned document but completely lack the “real-world noise” expected with physical paper-based workflows. The much crisper images appear almost perfect without random artifacts or background noise, and with the exact same amount of image skew across multiple pages. Thanks to the borders around each page of text, page skew can easily be measured, such as with VOL00007\IMAGES\0001\EFTA00009229.pdf. It is highly likely these PDFs were created by rendering original content (from a digital document) to an image (e.g., via print to image or save to image functionality) and then applying image processing such as skew, downscaling, and color reduction.

Re:A case study in PDF forensics: The Epstein PDFs by tombrossman on Wednesday February 04, 2026 @02:32PM (#46890493)
GNOME Desktop users can put this in a Bash script in ~/.local/share/nautilus/ for more convincing looking fake PDF scans, accessible from your right-click menu. I do not recall where I copied it from originally to give credit so thanks, random internet person (probably on Stack Exchange). It works perfectly.

  ROTATION=$(shuf -n 1 -e '-' '')$(shuf -n 1 -e $(seq 0.05 .5))

  for pdf in "$@";
    do magick  -density 150 $pdf \
              -linear-stretch '1.5%x2%' \
              -rotate 0.4 \
              -attenuate '0.01' \
              +noise  Multiplicative \
              -colorspace 'gray' \
              "${pdf%.*}-fakescan.${pdf##*.}"
  done
Re:A case study in PDF forensics: The Epstein PDFs by barrkel on Wednesday February 04, 2026 @04:11PM (#46891832)
That seq is probably supposed to be $(seq 0.05 0.05 0.5). Right now it's always 0.05.

Note that you can get random numbers straight from bash with $RANDOM. It's 15 bit (0 to 32767) but good enough here; this would get between 0.05 and 0.5: $(printf "0.%.4d\n" $((500 + RANDOM % 4501)))

Re:A case study in PDF forensics: The Epstein PDFs by streetfighter64 on Wednesday February 04, 2026 @03:31PM (#46891262)
Shouldn't $ROTATION be set inside the loop and actually used in the magick command?
Re:A case study in PDF forensics: The Epstein PDFs by tombrossman on Wednesday February 04, 2026 @03:58PM (#46891672)
You know, now that you point it out that seems obvious. I think maybe I was experimenting with rotation and left that in, unused. I did this years ago. The loop works OK though. Thanks for the feedback (and now I have to finish editing that script ...)
Re:A case study in PDF forensics: The Epstein PDFs by lordgrenville on Thursday February 05, 2026 @02:46AM (#46896881)
Nothing about this is specific to GNOME, right? Imagemagick is cross-platform
Re:A case study in PDF forensics: The Epstein PDFs by turboponyy on Thursday February 05, 2026 @04:15AM (#46897561)
I guess the Gnome-specific part is that Gnome comes with the Nautilus file browser, and the instructions add a script for Nautilus.

But yea, this will work as long as you have imagemagick and Nautilus installed.

Re:A case study in PDF forensics: The Epstein PDFs by lordgrenville on Thursday February 05, 2026 @04:50AM (#46897825)
Oh I missed that part, was just looking at the script
Re:A case study in PDF forensics: The Epstein PDFs by landdate on Thursday February 05, 2026 @10:46AM (#46900945)
or just run script and input pdf as argument...
Re:A case study in PDF forensics: The Epstein PDFs by mimischi on Thursday February 05, 2026 @10:17AM (#46900584)
Re:A case study in PDF forensics: The Epstein PDFs by landdate on Thursday February 05, 2026 @10:53AM (#46901017)
Another example of an idiot who has no clue how to use bash making basic mistakes.

Beautiful language ruined by morons.

Fix for idiots:

  do magick  -density 150 "${pdf}" \
Otherwise special characters or spaces in filename could mess up command.
Re:A case study in PDF forensics: The Epstein PDFs by landdate on Thursday February 05, 2026 @11:02AM (#46901114)
also why do morons never quote things?

  ROTATION=$(shuf -n 1 -e '-' '')$(shuf -n 1 -e $(seq 0.05 .5))
and this line is a mess easy fix if you aren't stupid.

  ROTATION="$(seq -0.5 0.05 0.5 | shuf -n 1)"
dumb fucks
Re:A case study in PDF forensics: The Epstein PDFs by taskforcegemini on Thursday February 05, 2026 @03:34PM (#46904836)
you sound as grumpy as my cat looks. there's no need for this language
Re:A case study in PDF forensics: The Epstein PDFs by streetfighter64 on Wednesday February 04, 2026 @01:41PM (#46889824)
Very interesting. That document in particular seems to be an interview of A. Acosta by the DoJ from 2019. But what reason would the FBI have for pretending it's a scanned document, if it is genuine? Perhaps there's some aspect of Epstein's deal with Acosta that they'd rather not reveal to the public?

https://www.justice.gov/epstein/files/DataSet%207/EFTA000092...

Re:A case study in PDF forensics: The Epstein PDFs by juujian on Wednesday February 04, 2026 @02:22PM (#46890388)
Not that I can speak from personal experience or anything... But somebody on an email chain may have requested a scanned version of the document to ensure there is no metadata and the employee might have found it easier to just flatten the pdf and apply a graphical filter to make the document appear like a scanned document. There might even be a webtool available somewhere to do so, I wouldn't know...
Re:A case study in PDF forensics: The Epstein PDFs by agopo on Wednesday February 04, 2026 @03:09PM (#46890946)
Stirling PDF has exactly that function: https://stirling.com/app/signup
Re:A case study in PDF forensics: The Epstein PDFs by ThePowerOfFuet on Wednesday February 04, 2026 @04:27PM (#46892048)
Straight to the signup page? A bit blatant, no?
Re:A case study in PDF forensics: The Epstein PDFs by mikkupikku on Wednesday February 04, 2026 @02:31PM (#46890486)
> the employee might have found it easier to just flatten the pdf and apply a graphical filter to make the document appear like a scanned document

Is that remotely plausible? I can't imaging faking a scan being easier than just walking down the hall to the copier room.

Re:A case study in PDF forensics: The Epstein PDFs by salynchnew on Wednesday February 04, 2026 @03:46PM (#46891495)
If it's already scanned, then you don't have to leave your desk.
Re:A case study in PDF forensics: The Epstein PDFs by ffsm8 on Wednesday February 04, 2026 @03:04PM (#46890885)
Depending on their technical capability, yes.

I mean even in this thread you got what are essentially one-liners to do it.

Definitely less hassle then doing it irl

Re:A case study in PDF forensics: The Epstein PDFs by streetfighter64 on Wednesday February 04, 2026 @03:49PM (#46891542)
Hoe big a percentage of FBI / DoJ employees are running linux (with imagemagick) as their work computer? I'd be surprised to see a similar oneliner for a stock windows installation.

Yeah they might have used some web converter, but that on the other hand would have been extremely incompetent handling of the secret data.

Re:A case study in PDF forensics: The Epstein PDFs by 1718627440 on Thursday February 05, 2026 @11:23AM (#46901342)
Installing MSYS2 is a matter of a few minutes. There is also WSL and macOS features a POSIX shell, imagemagick is likely already installed as a dependency somewhere, like ffmpeg often also is.
Re:A case study in PDF forensics: The Epstein PDFs by mikkupikku on Wednesday February 04, 2026 @04:58PM (#46892405)
I know I'm not the brightest bulb by any measure, but do some people really take less than at least a few minutes to come up with one-liners for problems as novel as graphical transformations to PDFs? Maybe if the presumed techie hacker / federal worker took it as an amusing challenge I could see this being done, but genuinely out of pure laziness? That's incredible if true.
Re:A case study in PDF forensics: The Epstein PDFs by naniwaduni on Wednesday February 04, 2026 @05:52PM (#46893035)
It's not a novel problem. But yes, I don't think people quite appreciate how quick and easy it is for people who are in the habit of brewing up one-liners to solve simple problems to do that. I've done it here on HN for jq toy problems before, and I don't really doubt there are people similarly familiar with imagemagick.
Re:A case study in PDF forensics: The Epstein PDFs by vlovich123 on Thursday February 05, 2026 @01:50AM (#46896530)
It’s a mix of “they’ve done it many times before” and these days AI. But remember the “they’ve done it many times before” just means that in a technical and popular forum you’re likely to find the handful of people who have done so regularly enough to remember the one liner. Also this is probably easily searchable as well so even prior to AI not super hard.
Re:A case study in PDF forensics: The Epstein PDFs by jeltz on Thursday February 05, 2026 @09:26AM (#46899959)
There is nothing novel about it. I saw at least one person say that they have done exactly the same thing out of laziness.
Re:A case study in PDF forensics: The Epstein PDFs by jojobas on Wednesday February 04, 2026 @05:18PM (#46892651)
It's thousands of pages, surely investing some time in a script is faster. They were in a rush as well.

If they were faking the documents rather than the delivery method they definitely could have invested some time in flawless looks.

Re:A case study in PDF forensics: The Epstein PDFs by smcnally on Wednesday February 04, 2026 @05:35PM (#46892872)
Or more-realistic flawed looks as the case is here.
Re:A case study in PDF forensics: The Epstein PDFs by meinersbur on Wednesday February 04, 2026 @05:24PM (#46892726)
The time advantage of faking a scan becomes better the more pages you have to scan.

https://xkcd.com/1205/

Re:A case study in PDF forensics: The Epstein PDFs by usr1106 on Thursday February 05, 2026 @02:45AM (#46896869)
Nice. But 5 years seems unrealistic. Who stays on the same job using same processes 5 years these days? Even if the task might remain the same, input formats might change, requiring extra maintenance to the tool. Should recalculate that for 3 years before using it in my automation decisions.
Re:A case study in PDF forensics: The Epstein PDFs by luplex on Thursday February 05, 2026 @03:12AM (#46897050)
you do not work in the public sector, where processes change rarely, slowly, and partially
Re:A case study in PDF forensics: The Epstein PDFs by normie3000 on Thursday February 05, 2026 @04:14AM (#46897553)
Working from home and no scanner in the house?
Re:A case study in PDF forensics: The Epstein PDFs by ongy on Thursday February 05, 2026 @06:37AM (#46898567)
No printer.
Re:A case study in PDF forensics: The Epstein PDFs by dahcryn on Thursday February 05, 2026 @04:15AM (#46897557)
If I look at my personal work situation, working from home would mean I can't do it immediately, but would have to remember to do it the next day. Or just do it digitally right now in a few minutes and have it off my to-do list

Don't attribute to malice what can be attributed to laziness, these are government workers

Re:A case study in PDF forensics: The Epstein PDFs by streetfighter64 on Thursday February 05, 2026 @04:59AM (#46897889)
I think maybe the old "don't attribute to malice" adage goes out the window when we're talking about a coverup of a giant child sex trafficking ring run by high-up people in the government.
Re:A case study in PDF forensics: The Epstein PDFs by sporkland on Thursday February 05, 2026 @12:03PM (#46901802)
While I don't disagree with your point about Epstein case being a massive cya for a ton of people in power, the fact is that if they deeply wanted to cover up something the right way to do it would to be to actually print it and scan it, this does look like someone shortcutted some broad order to print and scan all digital media.
Re:A case study in PDF forensics: The Epstein PDFs by Spooky23 on Thursday February 05, 2026 @07:13AM (#46898811)
You’re talking about 1,000 FBI agents locked in a building. There’s no printer.
Re:A case study in PDF forensics: The Epstein PDFs by juujian on Thursday February 05, 2026 @07:25PM (#46907417)
Look, what I'm saying is that I don't have a scanner at home or at work and I've find this.
Re:A case study in PDF forensics: The Epstein PDFs by breppp on Thursday February 05, 2026 @09:45AM (#46900194)
I am only guessing that they had to remove the document from a classified network in a way where data won't possibly leak
Re:A case study in PDF forensics: The Epstein PDFs by hiccuphippo on Wednesday February 04, 2026 @04:43PM (#46892231)
I mean, I do that all the time when they ask me to print something, sign it, and then scan it.

Sign a blank paper, scan it, paste the original doc on it. Then keep the scan for future docs.

Re:A case study in PDF forensics: The Epstein PDFs by foxglacier on Thursday February 05, 2026 @01:52AM (#46896545)
An easier trick I've used is just sign directly on the computer screen over the displayed document with a whiteboard marker and take a photo with my phone.
Re:A case study in PDF forensics: The Epstein PDFs by nullbio on Thursday February 05, 2026 @03:23AM (#46897126)
The real question is: Which of the documents are the ones that are "simulating" scanned documents, and what political narrative do they reinforce?

The only reason I can think of for why someone would want to do this is to pass off fraudulent or AI generated images as real.

Re:A case study in PDF forensics: The Epstein PDFs by reactordev on Thursday February 05, 2026 @05:25AM (#46898078)
This. Slip in a few thousand “fakes” with the trove of goods to be able to fabricate a narrative.
Re:A case study in PDF forensics: The Epstein PDFs by boromisp on Thursday February 05, 2026 @07:22AM (#46898860)
A simpler explanation could be wanting to skip the print->sign->scan ceremony required by some institutions.
Re:A case study in PDF forensics: The Epstein PDFs by lucideer on Friday February 06, 2026 @10:20AM (#46913906)
Another explanation is that it's simply one form of lazy ineffective obfuscation performed by inexperienced relative luddites in an attempt to walk the fine line between complying with the supreme court directive & not releasing anything useful.

Other investigations into the files have found oddities like redaction of the word "don't" indicating a haphazard find-&-replace approach to redaction, possibly LLM-aided.

The DOJ/Akamai online hosted search feature is also incomplete - potentially due to some of these "digitally scanned" files not being subject to OCR.

Re:A case study in PDF forensics: The Epstein PDFs by lucideer on Friday February 06, 2026 @10:23AM (#46913941)
> to pass off fraudulent or AI generated images as real.

Possibly but I don't find it compelling, if only because a significant portion of the media reportage on the files has made claims that are entirely baseless - if there were a narrative to be sold one would expect such reportage to be actively leveraging such fraudulent images.

Re:A case study in PDF forensics: The Epstein PDFs by zoky on Thursday February 05, 2026 @05:35AM (#46898138)
Such a weird way to do it when it would be a vastly easier to just blow the document out to paper and re-scan it.
Re:A case study in PDF forensics: The Epstein PDFs by brazzy on Thursday February 05, 2026 @05:46AM (#46898221)
Vastly easier when you do it to one or a handful of documents.

But if you want to do it to 2000 documents...

Re:A case study in PDF forensics: The Epstein PDFs by pbhjpbhj on Thursday February 05, 2026 @07:20AM (#46898847)
4 reems (4×500) is hardly a lot for commercial equipment to handle - paper trays will take a reem at a time. Document analysis would still show some shenanigans were in play, but you'd get a bit of variation at least.
Re:A case study in PDF forensics: The Epstein PDFs by fc417fc802 on Thursday February 05, 2026 @11:27AM (#46901384)
But at that point why bother with the fakery? Why does it matter if it's obviously of digital origin? As long as it's rendered down to an image problem solved.

Was the motivation for this benign (an employee skirting regulations) or malicious?