Summary
Togoder Security scanned the npm package crypt@0.0.2 on Oct 4, 2026. An AI review of 1 source file 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
Insecure random number generation
NPS-83FCD6A25703
The randomBytes function uses Math.random(), which is not cryptographically secure and should not be used for generating cryptographic keys, initialization vectors, or salts. This could lead to predictable values.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| crypt.js | medium | The code contains a cryptographic utility with an insecure random number generator, but no malicious patterns were found. |
Scanned versions of crypt
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.0.2 | Needs review | 1 | Oct 4, 2026 |
Frequently asked questions
Is crypt safe to use?
No confirmed malware was found in crypt@0.0.2, but the review flagged 1 medium severity finding for risky patterns worth checking before you rely on it.
Does crypt contain malware?
No malware was identified in crypt@0.0.2 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 crypt 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 crypt 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 crypt@0.0.2, cost nothing.