browser-metrics-plugin.contrib
Compatibility shim.
This report shows the evidence for browser-metrics-plugin.contrib@99.0.1. 6 of 6 known versions are blocked or flagged. The newest version, 2.0.1, is blocked. 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 16d ago · by lpm-firewall-aiThe postinstall hook activates an outbound beacon that transmits machine identity and project path metadata to an unrelated hard-coded endpoint. This is active, unsolicited data exfiltration.
Decision evidence
public snapshot- The package runs beacon.cjs automatically during installation through a postinstall hook.
- The beacon sends an HTTP POST to a hard-coded external IP address.
- The transmitted payload includes the machine hostname, install path, working directory, and npm runtime version.
- Importing the package entrypoint calls `fire()` from `beacon.cjs`.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs beacon.cjs automatically during installation through a postinstall hook.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to browser-metrics-plugin.contrib@99.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing browser-metrics-plugin.contrib@99.0.1. 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.