@bcryptln/bcryptjs
Optimized bcrypt in plain JavaScript with zero dependencies, with TypeScript support. Compatible to 'bcrypt'.
This report shows the evidence for @bcryptln/bcryptjs@3.0.3. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe appended obfuscated payload executes automatically on import and deliberately exposes Node runtime capabilities to concealed code. This is a concrete unauthorized execution chain, despite no lifecycle hook or plaintext endpoint.
Decision evidence
public snapshot- `index.js:1161` appends a large obfuscated payload after the bcrypt implementation.
- The payload reconstructs hidden strings, obtains a dynamic `Function` constructor, and invokes generated code at import time.
- It exposes `require`, `module`, `__dirname`, and `__filename` through `global` before hidden-code execution.
- `package.json` exports `index.js` for ESM consumers, so importing the package triggers the payload.
- `package.json` contains no preinstall/install/postinstall lifecycle hook.
- Visible `index.js` code before the appended payload implements bcrypt hashing and crypto randomness.
- `bin/bcrypt` only hashes its explicit command-line input.
- No plaintext network endpoint or file-harvesting path was recoverable from the inspected source.
Source & flagged code
1 flagged · loading sourceSource contains an obfuscator-style string-array loader that reconstructs and executes hidden code.
index.jsView on unpkg · L1160Findings
Affected versions and remediation
This report applies to @bcryptln/bcryptjs@3.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing @bcryptln/bcryptjs@3.0.3. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.