@rutxploit-sec/subsplash-sentry
BUGBOUNTY PoC — represents @subsplash/sentry — @subsplash/sentry (62 refs in bundles) — Subsplash report 7a8faa0b
This report shows the evidence for @rutxploit-sec/subsplash-sentry@1.0.0, the only known version.
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe preinstall hook unconditionally exfiltrates hostname and username to a listener and suppresses errors, which is concrete install-time data collection. A loopback URL and bug-bounty wording do not make that install behavior consented or harmless.
Decision evidence
public snapshot- npm preinstall runs a node one-liner that reads the machine hostname and OS username and sends them in a GET query to http://127.0.0.1:8099, labeled as package @subsplash/sentry.
- The same preinstall hook discards stderr with 2>/dev/null and prints a dependency-confusion execution banner.
- index.js, loaded via main, logs that @subsplash/sentry was loaded from the public npm registry and exports an empty object.
- The callback host is loopback 127.0.0.1 rather than a remote collector.
- index.js imports os but does not read or send hostname or username when the module is required.
- No file writes, credential-file reads, or runtime self-dependency are present.
Source & flagged code
6 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgnpm preinstall runs a node one-liner that reads the machine hostname and OS username and sends them in a GET query to http://127.0.0.1:8099, labeled as package @subsplash/sentry.
Findings
Affected versions and remediation
This report applies to @rutxploit-sec/subsplash-sentry@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @rutxploit-sec/subsplash-sentry@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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.