The endpoint receives the local account name without the installer's consent.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The automatic postinstall request sends the local username to a request-catcher endpoint, which is unauthorized install-time data exfiltration. The runtime entry point is benign, but it does not change the install hook's behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Runs automatically during package installation via `postinstall`.
Mechanism
A `curl` request embeds the output of `whoami` in the URL query parameter `user`.
Attack narrative
On installation, the postinstall hook runs `whoami` and sends the result to a request-catcher host in a `curl` request. This discloses the installer's local username without consent.
Evidence
package.json
Network endpoints1
asdasdasdasdasdasdasfafdfdg.requestcatcher.com
Decision evidence
public snapshot
Evidence for block
The postinstall script sends the local username from `whoami` to `asdasdasdasdasdasdasfafdfdg.requestcatcher.com` without installer consent.
Evidence against
The `index.js` entry point only exports a function that logs a success message.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 120 B of source
Findings
3 high · 1 medium · 1 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @nuri.yavuz.tr.2/my-unique-pinger@1.0.2. 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.