Summary
Togoder Security scanned the npm package cookie-signature@1.0.6 on Oct 4, 2026. An AI review of 1 source file produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | This is the standard cookie-signature npm package implementation; it performs HMAC-SHA256 signing and verification with no malicious patterns, no network access, no process spawning, and no filesystem manipulation. |
Affected version ranges
None of the 3 scanned versions of cookie-signature are flagged high or critical. The latest scanned version, 1.2.2, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 1.2.2 | No issues | 1 | 1.2.2 | |
| 1.0.7 | Needs review | 1 | 1.0.7 | Weak cryptographic comparison |
| 1.0.6 | No issues | 1 | 1.0.6 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of cookie-signature
Frequently asked questions
Is cookie-signature safe to use?
Our AI source review of cookie-signature@1.0.6 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does cookie-signature contain malware?
No malware was identified in cookie-signature@1.0.6 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 cookie-signature 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 cookie-signature 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 cookie-signature@1.0.6, cost nothing.