Summary
Togoder Security scanned the npm package string.prototype.includes@2.0.1 on Oct 6, 2026. An AI review of 5 source files produced 1 medium severity finding. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.
Findings 1
Dynamic module loading / import-time side effect
NPS-76A9D1E46D57
The file immediately requires './shim' and invokes it on import. This executes code from an external module at load time. While the current file itself is a thin wrapper for the 'includes' polyfill, the behavior depends entirely on the contents of the './shim' module, which is not provided for inspection. Import-time side effects from an unreviewed dependency are a potential vector for hidden malicious behavior.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| auto.js | medium | The file is a minimal wrapper that executes an external './shim' module at import time; it is not inherently malicious, but its safety cannot be fully verified without inspecting the shim it loads. |
| implementation.js | safe | Cleared by Jev triage; no further analysis needed |
| index.js | safe | No malicious patterns detected; the file is a standard polyfill wrapper for Array.prototype.includes with no network, filesystem, process, or dynamic execution behavior. |
| polyfill.js | safe | No malicious patterns detected |
| shim.js | safe | This is a legitimate ES6 String.prototype.includes polyfill shim with no malicious patterns detected. |
Frequently asked questions
Is string.prototype.includes safe to use?
No confirmed malware was found in string.prototype.includes@2.0.1, but the review flagged 1 medium severity finding for risky patterns worth checking before you rely on it.
Does string.prototype.includes contain malware?
No malware was identified in string.prototype.includes@2.0.1 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 string.prototype.includes checked?
Togoder Security downloaded the published npm package and had an AI model read its 5 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 string.prototype.includes 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 string.prototype.includes@2.0.1, cost nothing.