registry / analytics-widget / 1.0.0

analytics-widget@1.0.0

AI Security Review

scanned 21d ago · by lpm-firewall-ai

Importing the module in a browser starts a two-second timer that reads an auth token or the full localStorage dump and POSTs it to /addPost. There is no other product behavior.

Static reason

No blocking static signals were detected.

Trigger

Requiring or importing index.js in a page that has localStorage.

Impact

Session tokens and other client-stored secrets are sent to the host app /addPost endpoint, where they can be stored or leaked.

Mechanism

Import-time localStorage token harvest and fetch POST

Attack narrative

analytics-widget@1.0.0 is a two-file package whose main entry runs immediately. After two seconds it pulls localStorage.getItem('token') or serializes all of localStorage, then fetch-POSTs that value to /addPost. That is credential theft on import, not an analytics widget. The relative URL still ships secrets off the page into whatever that endpoint records.

AI rationale

Inspected source shows import-time localStorage token theft and a fetch POST with no legitimate widget code. That is concrete credential exfiltration, so the package is blocked.

Evidence

index.jspackage.json

Network endpoints1

/addPost

OSV advisory

OpenSSF/OSV

Advisory

MAL-2026-17163

Source

The package is published as 'analytics-widget' with an empty description, but its main module contains no analytics functionality. On load, index.js schedules a 2-second timer that reads the 'token' key from browser localStorage, falls back to a JSON serialization of the entire localStorage store if that key is missing, and POSTs the result to the relative endpoint '/addPost' via fetch. When bundled into a consumer's frontend, every end-user session that loads the page has their auth token (or the full localStorage contents) sent to whichever origin serves the bundle, enabling session hijacking of the consuming application's users. The package name and empty metadata serve as a cover story; no legitimate analytics code is present. ## Source: ghsa-malware (399579776689b5ab6b5fe78e2c79da4ddf4950f898e9017333bdadaf3603a7f3) 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.

analytics-widget@1.0.0

AI Security Review

OSV advisory

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code