Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

spf-analyticsnpm

Advisory published Updated

spf-analytics is a confirmed malicious npm package (MAL-2026-14486) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spf-analytics (npm)

MAL-2026-14486
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall spf-analytics

What this malware does

index.js is a heavily obfuscated browser script (obfuscator.io-style string-array + rotation) advertised for inclusion via unpkg on Shopify-style storefronts. At runtime it listens for the 'gokwik_events' window event and harvests customer name, phone, email, full address, city, state, country, pincode, cart line items, order total, and payment method. The captured PII is encrypted with a hardcoded RSA-OAEP public key wrapping an AES-GCM session key and POSTed to https://connector.internalwebhooks.com/spf-analytics, a destination the storefront operator did not configure. A localStorage key ('shopify_analytics_cache_7f4c91d8b2e64a0f9c37d5ab81e26f43') holds up to 500 fingerprints to suppress duplicate uploads, and a __spfAddressForwarderLoaded flag guards against double-loading. The endpoint URL, PEM key, event name, and field names are all indirected through the obfuscator string table, concealing the destination and captured fields from casual inspection of the CDN-served bundle. The package presents itself as 'analytics' but the relay is to a non-first-party endpoint hardcoded by the author, encrypted to prevent network inspection, and never disclosed to the operator embedding the script.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

8dece44c5ce884af66714dbff1f022e0345e860d0090cb7bcb30fd7b352cdd77
80bf3cd2f3401671c464f9ff2b58588e8f4c6b29cf36ad71e841e42abb706241

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for spf-analytics (version 1.0.0).

  2. If you installed it — respond

    spf-analytics is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If spf-analytics was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. spf-analytics on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018732GHSA-fj97-8h42-crgr

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks spf-analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

spf-analytics (npm) malicious package — MAL-2026-14486 | O3 Security