The recipient receives identifying information about the installing machine and project context.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
Source inspection confirms automatic, unconsented disclosure of identifying host and installation metadata to a fixed external recipient. This supports blocking publication for data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation, or importing index.js.
Mechanism
beacon.cjs collects machine and installation context and sends it in a POST request to the configured endpoint.
Attack narrative
The postinstall hook runs the beacon automatically. The beacon sends the host name, installation path, working directory, and package-manager version to a fixed external IP address. Importing the package also fires the beacon, so the disclosure is not limited to installation.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs beacon.cjs automatically through its postinstall hook.
The beacon sends a POST request to a fixed external IP address.
The transmitted payload includes the host name, installation path, working directory, and package-manager version.
Importing index.js also fires the beacon.
Evidence against
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.29 KB of source
1 external domain referenced
185.158.107.175
Findings
8 high · 1 medium · 2 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @ppa-web-components/ppa-banner@0.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.