@onefootprint/footprint-js@6.1.0
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package’s onboarding and authentication requests to its own API match its stated purpose, and no install-time behavior was found. However, runtime warning and error telemetry sends the current page URL and optional client context to the vendor without an evident disclosure, so this is suspicious telemetry rather than malicious credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Warnings or errors during SDK use, including onboarding; local hosts are excluded.
Impact
The vendor receives page URL and runtime diagnostic data without an evident disclosure or opt-out in the inspected package.
Mechanism
The SDK posts error details and optional context to api.onefootprint.com/org/sdk_telemetry. The telemetry payload includes the current page URL, which can contain identifying path or query data.
AI rationale
The package’s onboarding and authentication requests to its own API match its stated purpose, and no install-time behavior was found. However, runtime warning and error telemetry sends the current page URL and optional client context to the vendor without an evident disclosure, so this is suspicious telemetry rather than malicious credential exfiltration.
Evidence
dist/footprint-js.cjs
Network endpoints1
api.onefootprint.com/org/sdk_telemetry
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Runtime warnings and errors are sent to the SDK telemetry API with the current page URL as tenantDomain.
- Error telemetry can include serialized context; the SDK also captures the browser URL and client details for that context.
- The telemetry request targets the package vendor’s /org/sdk_telemetry endpoint.
- Telemetry is sent during onboarding initialization after the caller supplies an onboarding session token.
Evidence against
- The manifest declares no install, preinstall, or postinstall hook.
- The onboarding flow uses the supplied session token with the package’s own API, consistent with the package’s identity-verification purpose.
Behavioral surface
DynamicRequireEnvironmentVarsEval
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
5 flaggeddist/footprint-js.umd.jsView file
3L4: var ju=Object.create;var _e=Object.defineProperty,$u=Object.defineProperties,Wu=Object.getOwnPropertyDescriptor,Xu=Object.getOwnPropertyDescriptors,Qu=Object.getOwnPropertyNames,Ie...
L5:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/footprint-js.umd.jsView on unpkg · L3dist/footprint-js.cjsView file
•Credential-bearing message sent to a fixed external iframe in dist/footprint-js.cjs:
var jd=Object.create;var Qe=Object.defineProperty,$d=Object.defineProperties,Wd=Object.getOwnPropertyDescriptor,Xd=Object.getOwnPropertyDescriptors,Qd=Object.getOwnPropertyNames,Ae...
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/footprint-js.cjsView on unpkg30,i=a?`${t} | context: ${a}`:t;yield Kt({body:{tenantDomain:o,sdkKind:e,sdkName:Nt,sdkVersion:Lt,logLevel:r,logMessage:i,sessionId:M()}});}catch(a){}});var je=()=>{try{let e=window.location.hostname;return e==="localhost"||e==="127.0.0.1"|
Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/footprint-js.cjs
MediumDynamic Requiredist/footprint-js.umd.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencedist/footprint-js.cjs
MediumAi Review Evidencedist/footprint-js.cjs
MediumAi Review Evidencedist/footprint-js.cjs
LowScripts Present
LowEval
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @onefootprint/footprint-js@6.1.0.
See all versions of @onefootprint/footprint-js for other recorded verdicts.
- Review the evidence and your use of @onefootprint/footprint-js@6.1.0 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.