Summary
Togoder Security scanned the npm package create-require@1.1.1 on Oct 4, 2026. An AI review of 1 source file produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
dynamic code execution
NPS-196B3D4F6CB7
The polyfill uses _compile to execute the string 'module.exports = require;', which is a dynamic code execution pattern. However, the string is static and not user-controlled, so it is not malicious. It is a known pattern for creating a require function.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| create-require.js | safe | The code is a legitimate polyfill for createRequire, but contains a minor dynamic code execution pattern using Module._compile with a static string, which is not malicious. |
Scanned versions of create-require
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.1.1 | No issues | 1 | Oct 4, 2026 |
Frequently asked questions
Is create-require safe to use?
Our AI source review of create-require@1.1.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does create-require contain malware?
No malware was identified in create-require@1.1.1 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was create-require checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 create-require 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 create-require@1.1.1, cost nothing.