registry / @prosopo/procaptcha-bundle / 4.4.3
@prosopo/procaptcha-bundle@4.4.3
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious signals are consistent with a CAPTCHA client bundle: browser initialization, configured environment values, and a named provider prefetch. Direct inspection found no install hook or concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Importing the browser bundle or rendering a CAPTCHA widget.
Impact
No package-originated file mutation, command execution, or unconsented data exfiltration was found.
Mechanism
Browser-side CAPTCHA widget initialization and provider-detector prefetch.
AI rationale
The suspicious signals are consistent with a CAPTCHA client bundle: browser initialization, configured environment values, and a named provider prefetch. Direct inspection found no install hook or concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes browser entrypoints and contains only build, serve, and test scripts, with no install lifecycle hook.
- The built entrypoint conditionally invokes a named Prosopo CAPTCHA dependency to prefetch a detector using a site key.
- On browser import, the code publishes a CAPTCHA widget API and dispatches a ready event.
Evidence against
- No source evidence of child-process execution, shell commands, eval, filesystem access, credential harvesting, or exfiltration.
- The environment-variable reads configure CAPTCHA settings; this package does not send values to an endpoint itself.
- No reviewer-directed text, self-dependency, persistence, or project mutation was found.
Behavioral surface
CryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/index.jsView file
5package = @prosopo/procaptcha-bundle; repositoryIdentity = captcha; dependency = @prosopo/procaptcha-common
L5: import { WidgetThemeResolver } from "./util/widgetThemeResolver.js";
L6: import { getWindowCallback } from "@prosopo/procaptcha-common";
L7: import { PROCAPTCHA_START_EVENT, StartModeEnum } from "@prosopo/types";
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L538var startDetectorPrefetch = (siteKey, flags) => {
if (!siteKey) return;
if (flags.startMode === StartModeEnum.manual) return;
Promise.all([import("@prosopo/procaptcha-frictionless"), import("@prosopo/procaptcha-common")]).then(([frictionless, common]) => {
frictionless.prefetchDetector(process.env.PROSOPO_DEFAULT_ENVIRONMENT, common.pickIpMode(flags), siteKey);
}).catch(() => void 0);
Low
Suspicious Dependency Evidence
The built entrypoint conditionally invokes a named Prosopo CAPTCHA dependency to prefetch a detector using a site key.
dist/index.jsView on unpkg · L38package.jsonView file
Findings
1 High2 Medium8 Low
HighCopied Package Dependency Bridgedist/index.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Dependency Evidencedist/index.js
LowAi Review Evidencesrc/index.ts
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.4.3.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.4.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.