Fooifier.exe getting flagged by antivirus software

Sophos Central Event Details
What happened: We could not clean up a potentially unwanted application (PUA).
Path: /var/lib/docker/overlay2/45ov8elabktydr0nmv81wsf5b/diff/~/.julia/packages/ObjectFile/lbue6/test/win32/fooifier.exe
What was detected: Generic ML PUA
User associated with device: n/a
How severe it is: Medium
What Sophos has done so far: We attempted to clean up a PUA.
What you need to do: In the Sophos Central Admin console, go to the Alerts page and find the PUA alert. Click on the PUA name to see details and cleanup advice on the Sophos website. Then go to the affected computer and clean up the PUA manually.

We are using ObjectFile only indirectly through Enzyme.jl (btw. it is not listed as a dependent on JuliaHub).
Could the binary test files use the artifacts system, only to be installed when running the tests, to avoid triggering these types of warnings in production systems only because ObjectFile.jl is installed deep in some dependency tree?

Start by locating the binary test files and how ObjectFile.jl currently includes them. Read Julia's artifacts system documentation and inspect the test setup to determine whether the binaries can be installed only when tests run. Done means production installations no longer include the test binaries while the tests still obtain and use them successfully.