sc-geeksquad-core
This report shows the evidence for sc-geeksquad-core@99.9.1. 2 of 3 known versions are blocked or flagged. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package declares a remote tarball dependency whose preinstall hook automatically transmits host, home-directory, and username identifiers to a fixed unrelated collector. This is an unconsented installation beacon and supports blocking publication.
Decision evidence
public snapshot- package.json installs ltidisafe from a remote tarball, whose manifest runs test.js during preinstall.
- test.js encodes the machine hostname, home directory, and username, then uses those values as subdomains of a fixed OAST host.
- The dependency’s index.js sends HTTP GET requests to the supplied URLs, activating the identifying-data disclosure during installation.
Source & flagged code
6 flagged · loading sourcepackage.json installs ltidisafe from a remote tarball, whose manifest runs test.js during preinstall.
package.jsonView on unpkg · L9Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to sc-geeksquad-core@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing sc-geeksquad-core@99.9.1. 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.