Summary
Togoder Security scanned the npm package function.prototype.name@1.1.8 on Oct 6, 2026. An AI review of 6 source files produced 3 medium, 1 low severity findings. 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 4
Indirect code execution via module import
NPS-9CF7B4A34E4F
The file immediately invokes the exported function from './shim' at top-level (require-time). Since './shim' is not shown, this shim module can execute arbitrary code upon loading, including installing hooks, monkey-patching globals, harvesting environment variables/credentials, or performing network requests. Top-level execution on import is a common vector for malicious npm packages.
Potential global environment modification
NPS-7E0C6CC45EFF
The term 'shim' typically implies modifying global objects or built-ins (e.g. patching process, console, require, or other prototypes). Such behavior can silently alter runtime semantics for the entire application, enabling interception of sensitive data or stealthy execution.
Opaque dependency
NPS-FC4236118E85
The actual behavior cannot be verified from this file alone — all logic resides in './shim'. The entry point provides no indication of what the shim does, which is a common obfuscation/encapsulation pattern in malicious packages.
Benign re-export
NPS-6CE13BF2A26A
This module simply re-exports the result of calling the 'functions-have-names' package. It is a thin compatibility shim with no data exfiltration, credential access, obfuscation, network activity, process spawning, or install-time side effects.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| auto.js | medium | The file is a thin wrapper that immediately executes an unspecified shim module at require-time, which is a potential vector for hidden malicious behavior such as credential harvesting, monkey-patching, or code execution, though no direct malicious code is visible. |
| helpers/functionsHaveNames.js | safe | No malicious patterns detected; the file is a benign compatibility re-export of the functions-have-names module. |
| implementation.js | safe | No malicious patterns detected; the code is a benign implementation of a Function.prototype.name sham/polyfill. |
| index.js | safe | No malicious patterns detected |
| polyfill.js | safe | Cleared by Jev triage; no further analysis needed |
| shim.js | safe | This is a legitimate ES5 polyfill for Function.prototype.name with no malicious patterns detected. |
Scanned versions of function.prototype.name
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.1.8 | Needs review | 6 | Oct 6, 2026 |
Frequently asked questions
Is function.prototype.name safe to use?
No confirmed malware was found in function.prototype.name@1.1.8, but the review flagged 3 medium, 1 low severity findings for risky patterns worth checking before you rely on it.
Does function.prototype.name contain malware?
No malware was identified in function.prototype.name@1.1.8 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 function.prototype.name checked?
Togoder Security downloaded the published npm package and had an AI model read its 6 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 function.prototype.name 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 function.prototype.name@1.1.8, cost nothing.