internal-renderers@1.0.0
Defensive placeholder. Benign beacon only (single HTTP GET to researcher server), no functional code. Held to prevent dependency-confusion abuse of an internal workspace package name exposed in a public repository. Will be transferred to the owning organi
AI Security Review
scanned 5d ago · by lpm-firewall-aiBoth install lifecycle hooks transmit the username, hostname, and working directory to a researcher server without installer consent. This is malicious install-time data exfiltration.
Decision evidence
public snapshot- Both preinstall and postinstall scripts send HTTP GET requests to 38.242.235.206 with the username, hostname, and current working directory.
- The README confirms the install scripts send those host and project details to a researcher server.
- The README describes the package as a defensive placeholder and says it contains no functional code beyond the beacon.
Source & flagged code
5 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to internal-renderers@1.0.0.
See all versions of internal-renderers for other recorded verdicts.
- Avoid installing internal-renderers@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.