Summary
Togoder Security scanned the npm package dompurify@3.4.16 on Oct 6, 2026. An AI review of 9 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/purify.cjs.js | safe | This is the legitimate DOMPurify HTML sanitization library (v3.4.16), containing only standard Babel-transpiled helpers and DOMPurify's documented sanitization logic with no malicious patterns such as exfiltration, credential harvesting, dynamic code execution, or install-time hooks. |
| dist/purify.es.mjs | safe | This is the legitimate DOMPurify 3.4.16 XSS sanitization library with no malicious patterns detected. |
| dist/purify.js | safe | No malicious patterns detected; this is a legitimate, unmodified build of DOMPurify 3.4.16 whose code performs HTML sanitization without any exfiltration, credential harvesting, obfuscated payloads, dynamic code execution, network calls, or process spawning. |
| src/attrs.ts | safe | Cleared by Jev triage; no further analysis needed |
| src/config.ts | safe | Cleared by Jev triage; no further analysis needed |
| src/regexp.ts | safe | Cleared by Jev triage; no further analysis needed |
| src/tags.ts | safe | Cleared by Jev triage; no further analysis needed |
| src/types.ts | safe | Cleared by Jev triage; no further analysis needed |
| src/utils.ts | safe | No malicious patterns detected; the code is a defensive utility library (DOMPurify-style) that hardens against prototype pollution and implements safe string/object operations. |
Frequently asked questions
Is dompurify safe to use?
Our AI source review of dompurify@3.4.16 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does dompurify contain malware?
No malware was identified in dompurify@3.4.16 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was dompurify checked?
Togoder Security downloaded the published npm package and had an AI model read its 9 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan dompurify together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in dompurify@3.4.16, cost nothing.