spf-analytics
Storefront analytics loader.
This report shows the evidence for spf-analytics@1.0.0, the only known version.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe published entrypoint silently forwards checkout PII to a hardcoded third-party webhook after encrypting it for the package operator. Obfuscation and the analytics label conceal that collection rather than document a user-controlled analytics client.
Decision evidence
public snapshot- package.json points main at index.js and sets sideEffects true, with no install lifecycle scripts, so the loader runs when a page includes the script.
- The obfuscated loader requires a phone, keeps a fingerprint cache, and takes its endpoint and public key from the hidden string table.
- Checkout parsing keeps a 10-digit phone that must start with 6-9, plus email, name, and full address fields.
- The collected address, order, and context are encrypted with an embedded RSA public key and AES-GCM, then posted with fetch to https://connector.internalwebhooks.com/spf-analytics.
- A window listener forwards events into that sender, and the string table contains gokwik_events.
- There are no preinstall, install, or postinstall hooks and no shell, eval, or environment harvesting.
- The request credentials value is chosen from the string table, which includes omit, so this posts a body rather than stealing cookies.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
index.jsView on unpkg · L1The obfuscated loader requires a phone, keeps a fingerprint cache, and takes its endpoint and public key from the hidden string table.
index.jsView on unpkg · L1Checkout parsing keeps a 10-digit phone that must start with 6-9, plus email, name, and full address fields.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to spf-analytics@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing spf-analytics@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.