The recipient learns the host name and package installation and working-directory paths without an affirmative consent check.
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 automatic installation-time disclosure of host and project identifiers to a hardcoded external recipient, with no consent guard. This supports blocking the package as an installation beacon.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package or importing index.js.
Mechanism
The postinstall hook runs beacon.cjs, which sends metadata in an HTTP POST; index.js also invokes the same beacon when imported.
Attack narrative
The postinstall hook activates a beacon that sends host and project path metadata to a hardcoded external IP address. Importing the package entrypoint also triggers the same send. No affirmative consent guard is present in the inspected activation paths.
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 from an automatic postinstall hook.
beacon.cjs sends a POST to a hardcoded external IP address.
The request sends package, hostname, install path, and working directory metadata.
Importing index.js also calls the beacon without a user consent check.
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@2.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.