Summary
Togoder Security scanned the npm package @sigstore/verify@3.1.1 on Oct 6, 2026. An AI review of 23 source files produced 1 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 2
Unanchored Regular Expression Matching
NPS-81D4BB6E9643
verifySubjectAlternativeName uses policyIdentity.match(policyIdentity) without anchoring. If the policyIdentity is user-controlled or constructed from untrusted input, an attacker could craft a pattern that matches unintended signer identities (e.g., 'evil.com' could match 'evil.com.attacker.com'), potentially bypassing certificate identity verification. The comment even warns callers to use anchored patterns, indicating this is a known risk.
Prototype Pollution in Extension Verification
NPS-9A433CACB7BA
verifyExtensions iterates over policyExtensions using a for..in loop without hasOwnProperty checks. If policyExtensions inherits from a polluted prototype, it could iterate over inherited properties and cause unexpected behavior or bypass verification. While this file is likely a policy helper rather than an entry point, prototype pollution from other modules could affect behavior here.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/policy.js | medium | The code is a certificate policy verification utility with no overt malicious patterns, but it uses unanchored regex matching for identity verification and an unguarded for..in loop, which could weaken security guarantees if misused. |
| dist/bundle/dsse.js | safe | No malicious patterns detected; the code is a benign DSSE signature content handler from the Sigstore project. |
| dist/bundle/index.js | safe | No malicious patterns detected; the code performs Sigstore bundle parsing and cryptographic verification without suspicious behavior. |
| dist/bundle/message.js | safe | No malicious patterns detected; the code is a legitimate Sigstore signature verification utility with no exfiltration, obfuscation, or unauthorized execution. |
| dist/error.js | safe | No malicious patterns detected |
| dist/index.js | safe | No malicious patterns detected; the file is a standard re-export module from the Sigstore JavaScript client with no obfuscation, network calls, or suspicious execution. |
| dist/key/certificate.js | safe | No malicious patterns detected |
| dist/key/index.js | safe | No malicious patterns detected; the code appears to be a legitimate Sigstore verification library with no exfiltration, credential harvesting, obfuscation, or suspicious behavior. |
| dist/key/sct.js | safe | No malicious patterns detected; the code is a legitimate Sigstore SCT verification implementation using standard X.509 certificate processing with no exfiltration, dynamic execution, or credential harvesting. |
| dist/shared.types.js | safe | No malicious patterns detected |
| dist/timestamp/index.js | safe | No malicious patterns detected; the code only wraps timestamp verification and formatting without any exfiltration, execution, or filesystem access. |
| dist/timestamp/tsa.js | safe | No malicious patterns detected; the code implements RFC 3161 timestamp verification using libraries and performs only certificate chain validation. |
| dist/tlog/checkpoint.js | safe | No malicious patterns detected; the file implements checkpoint verification for Sigstore transparency logs using standard cryptographic operations and input validation. |
| dist/tlog/dsse.js | safe | No malicious patterns detected; the code is a standard Sigstore DSSE tlog verification module with no network, filesystem, process, or dynamic execution behavior. |
| dist/tlog/hashedrekord.js | safe | The code is a Sigstore transparency log verification module with no malicious patterns, network calls, process spawning, or obfuscation detected. |
| dist/tlog/index.js | safe | This is a legitimate Sigstore transparency log verification module with no malicious patterns detected. |
| dist/tlog/intoto.js | safe | No malicious patterns detected |
| dist/tlog/merkle.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/tlog/set.js | safe | This is a legitimate Sigstore transparency log SET verification module with no malicious patterns, no external network calls, no credential harvesting, and no dynamic code execution. |
| dist/trust/filter.js | safe | No malicious patterns detected |
| dist/trust/index.js | safe | No malicious patterns detected; the code is a standard Sigstore trust material utility with no exfiltration, credential harvesting, obfuscation, or process execution. |
| dist/trust/trust.types.js | safe | No malicious patterns detected |
| dist/verifier.js | safe | No malicious patterns detected; the code is a legitimate Sigstore verification library with no data exfiltration, credential harvesting, dynamic code execution, or other security concerns. |
Frequently asked questions
Is @sigstore/verify safe to use?
No confirmed malware was found in @sigstore/verify@3.1.1, but the review flagged 1 medium, 1 low severity findings for risky patterns worth checking before you rely on it.
Does @sigstore/verify contain malware?
No malware was identified in @sigstore/verify@3.1.1 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 @sigstore/verify checked?
Togoder Security downloaded the published npm package and had an AI model read its 23 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 @sigstore/verify 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 @sigstore/verify@3.1.1, cost nothing.