The collector receives identifying host and project path information during installation or import.
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 confirms unconsented install-time disclosure of host and project identifiers to a hardcoded external collector, with no apparent package function requiring that transfer. This is concrete data exfiltration behavior and warrants blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall hook; importing index.js also invokes the report.
Mechanism
beacon.cjs posts the package name, hostname, installation path, working directory, and npm version to a hardcoded endpoint without a consent check.
Attack narrative
The package automatically runs a provenance beacon after installation and also fires it when its entrypoint is imported. The beacon sends the machine hostname and local installation and working directory paths to a fixed external IP address. No consent gate is present in the inspected trigger or reporting function.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs beacon.cjs automatically through a postinstall hook.
beacon.cjs sends a POST request to the fixed external endpoint 185.158.107.175:8787/_ah/dc.
The payload includes the machine hostname, installation path, working directory, package name, and npm version.
Running beacon.cjs directly calls fire(), and importing index.js also calls fire().
Evidence against
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.30 KB of source
1 external domain referenced
185.158.107.175
Findings
9 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-hotel-collection@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.