Is SentinelOne flagging your website or file?
If SentinelOne is flagging your site or a file — often showing up as “Static AI – Suspicious/Malicious PE”, DFI (Deep File Inspection) labels — it is either a real infection or a false positive from a past issue. Here is how to get it cleared.
Step 1 — Confirm it is really a false positive
Do not request removal while malware is still present, or the flag returns. Check first:
- Run my free Is My Site Hacked? checker.
- Cross-check on VirusTotal to see every engine flagging you.
If anything turns up, get it fully cleaned first — deleting the visible malware is not enough if a backdoor remains.
Step 2 — Report the false positive to SentinelOne
SentinelOne takes VirusTotal-engine false positives by email; customers use a support-portal ticket. Submit here: report@sentinelone.com (email)
- Verify the “SentinelOne (Static ML)” flag on VirusTotal.
- Email report@sentinelone.com with the VT link, SHA-256, and legitimacy evidence.
- Managed customers should open a ticket in the SentinelOne portal (routed to the detection team).
- Add an exclusion/allowlist in-console as an interim fix.
- Keep the agent current with Live Security Updates.
Good to know: report@sentinelone.com is the VirusTotal-engine channel; for endpoints the official route is a support-portal ticket.
Step 3 — If the warning keeps coming back
A detection that returns after you have been cleared almost always means the infection was never fully removed — usually a backdoor in a theme file, a rogue admin user, or malware in the database. That is exactly what I fix. I am a USA-based WordPress security specialist: I remove the infection completely, submit the delisting on your behalf, and harden the site so it stays clean.
Get my site cleaned · See how it works · read my client reviews.
Frequently asked questions
How long does SentinelOne take to clear a false positive? Once the site/file is genuinely clean and you have submitted the request, most are resolved within a few days. Submitting while still infected only restarts the clock.
It keeps coming back — why? Because the real infection (a backdoor, rogue admin, or database payload) is still there. A full cleanup stops the loop.