ecobee-home
Utility package
This report shows the evidence for ecobee-home@0.0.2. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no apparent functionality beyond an unconsented install-time hostname beacon to an unrelated hard-coded endpoint. This is concrete data exfiltration behavior.
Decision evidence
public snapshot- postinstall executes beacon.js.
- beacon.js sends the host hostname to a hard-coded remote HTTP endpoint during installation.
- The network error is silently ignored.
- No other package source files or documented functionality were present.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgbeacon.js sends the host hostname to a hard-coded remote HTTP endpoint during installation.
beacon.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to ecobee-home@0.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing ecobee-home@0.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.