rn-push-provisioning
Security research - dependency confusion proof of concept. Contact: liquid2@liquidsec.net
This report shows the evidence for rn-push-provisioning@99.0.2. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. 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 2mo ago · by lpm-firewall-aiThis is unconsented install-time collection and transmission of local system identity data to a hard-coded external endpoint. The package has no legitimate implementation beyond this beacon.
Decision evidence
public snapshot- A preinstall hook runs beacon.js during npm installation.
- The install script collects the host name, local user name, platform, and CPU architecture.
- It sends the collected device data to a hard-coded external HTTP endpoint.
- The package contains no additional runtime functionality or payload files.
- No credential files, environment variables, shell commands, or destructive actions were found.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA preinstall hook runs beacon.js during npm installation.
package.jsonView on unpkg · L6Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to rn-push-provisioning@99.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing rn-push-provisioning@99.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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.