ecobee-api
Utility package
This report shows the evidence for ecobee-api@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-aiThis is concrete, unconsented install-time host-data exfiltration disguised as a placeholder package. It warrants blocking.
Decision evidence
public snapshot- package.json runs beacon.js automatically during postinstall.
- beacon.js reads the host name and sends it to an external raw-IP HTTP endpoint, while suppressing errors.
- README identifies the package only as a placeholder; no legitimate runtime functionality is supplied.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs beacon.js automatically during postinstall.
package.jsonView on unpkg · L6beacon.js reads the host name and sends it to an external raw-IP HTTP endpoint, while suppressing errors.
beacon.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to ecobee-api@0.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing ecobee-api@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.