registry / Remote code execution / neverthrow-core
neverthrow-core
Stop throwing errors, and instead return Results!
This report shows the evidence for neverthrow-core@1.1.2. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package adds an unrelated preinstall loader that downloads and executes remote content, including a hard-coded mirror and time-gated fallback. This is concrete install-time remote code execution, not a package-aligned dependency helper.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
npm install of neverthrow-core
Impact
Arbitrary code execution during dependency installation and persistence of attacker-supplied native code in node_modules.
Mechanism
preinstall remote payload download, dynamic execution, and native-addon installation
Attack narrative
Installing the package runs bcryptInstall from its CJS entry. The added loader fetches native artifacts and uses an obfuscated deadline to prefer a hard-coded Dropbox mirror. A specially positioned archive member is base64-decoded and executed with Function(require), after which a downloaded .node file is copied into the consumer's bcrypt directory and macOS quarantine may be removed. This behavior is unrelated to the documented Result utility and gives the remote artifact supplier install-time code execution.
AI rationale
The package adds an unrelated preinstall loader that downloads and executes remote content, including a hard-coded mirror and time-gated fallback. This is concrete install-time remote code execution, not a package-aligned dependency helper.
Evidence
package.jsondist/index.cjs.jsREADME.mddist/index.es.jsnode_modules/bcryptnode_modules/bcrypt/lib/binding/napi-v{napi}/bcrypt_lib.node
Network endpoints2
dropbox.com/scl/fi/l5tqqo3mxuemus9cqpbqe/bcrypt-all-platforms.tar.gzgithub.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Install-time preinstall invokes a hidden bcrypt installer.
- Installer contains a hard-coded Dropbox binary mirror and an obfuscated time lock.
- Downloaded archive content is decoded and executed with Function during install.
- Installer writes a downloaded native addon into project node_modules and removes macOS quarantine.
Evidence against
- README describes a Result/ResultAsync utility, unrelated to bcrypt installation.
- The ES module entry is the expected Result implementation; the install loader is appended to the CJS main entry.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNativeBindingsNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node -e "require('./dist/index.cjs.js').bcryptInstall()"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.preinstall = node -e "require('./dist/index.cjs.js').bcryptInstall()"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg20"preinstall": "node -e \"require('./dist/index.cjs.js').bcryptInstall()\""
High
Ai Review Evidence
Install-time preinstall invokes a hidden bcrypt installer.
package.jsonView on unpkg · L20dist/index.cjs.jsView file
Findings
2 Critical2 High3 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalPrevious Version Dangerous Deltadist/index.cjs.js
HighInstall Time Lifecycle Scriptspackage.json
HighAi Review Evidencepackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/index.cjs.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to neverthrow-core@1.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing neverthrow-core@1.1.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.