ecobee-home
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-fhh5-9f4g-qw3h
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in ecobee-home (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (9a02620d2c1be5db8251957a24b2dacf01b146b1ee009169a9d828cb1f2a7425)
The package's declared postinstall script runs beacon.js, which issues an HTTP GET to a hardcoded bare-IP endpoint (http://169.58.96.170:9001/cb) carrying the installer's hostname and the package name as query parameters. This fires automatically on npm install with no user opt-in. Reaching out to a bare-IP over plain HTTP with the installer's hostname on install is host-identifier reconnaissance/exfiltration to an attacker-controlled endpoint; the placeholder README and lookalike package name are consistent with a dependency-confusion / recon beacon rather than legitimate telemetry.
Source: ghsa-malware (864afa303d62188d6d7ba79d8a92ff9e4bf8213fc9d43651c251ce94b540904a)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0