@s4yhiitestpoc/scan-https-d
Research sample: postinstall sends a minimal install fingerprint over HTTPS to a researcher-controlled endpoint. No credentials or environment variables are read.
This report shows the evidence for @s4yhiitestpoc/scan-https-d@1.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe postinstall hook automatically discloses host-identifying data to a publisher-selected external collector without a source-enforced consent guard. This supports blocking as install-time data exfiltration.
Decision evidence
public snapshot- The package runs postinstall.js from its npm postinstall hook.
- The script collects the install directory, working directory, host and user names, platform details, DNS servers, and local network addresses.
- It posts the collected report to collector.oob.s4yhii.com and also makes a DNS query under oob.s4yhii.com.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs postinstall.js from its npm postinstall hook.
package.jsonView on unpkg · L7Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @s4yhiitestpoc/scan-https-d@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @s4yhiitestpoc/scan-https-d@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.