This is a bit annoying. Looks like some bad guys may be using dompdf (or aping it's PDF structure) to generate PDFs used in phishing scams. If that's the case and a sufficient number of similar documents are reported then it's likely that some anti-virus vendors will start using the dompdf-generated PDF characteristics in their signatures.
Here's a report on VirusTotal relating to a similar PDF:
https://www.virustotal.com/en/file/44231673527f6f9437df1789bca295efac86b9df1df0a68ccf06f5d48b732e10/analysis/Of course, the source lists a ridiculous number of potential issues using automated reporting just because Adobe Acrobat was opened to read the file
https://www.hybrid-analysis.com/sample/44231673527f6f9437df1789bca295efac86b9df1df0a68ccf06f5d48b732e10?environmentId=3There are other similar reports out there. Probably the best course of action is to contact your vendor and let them know that legitimate files are being flagged as malicious. It might help to point out what dompdf is and how to identify files produced by the library. We can help if needed.
It would be pretty destructive to the project if dompdf-generated PDF files started getting flagged as malicious by a significant number of anti-virus apps because of this. Who wants to use a library when the files it produces are causing these types of problems?