Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ecobee-homenpm

Advisory published Updated

ecobee-home is a confirmed malicious npm package (MAL-2026-14475) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecobee-home (npm)

MAL-2026-14475
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ecobee-home

What this malware does

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.

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.

Malicious versions

2 flagged
0.0.10.0.2

Indicators of compromise (SHA-256)

9a02620d2c1be5db8251957a24b2dacf01b146b1ee009169a9d828cb1f2a7425
864afa303d62188d6d7ba79d8a92ff9e4bf8213fc9d43651c251ce94b540904a
b3c26f716b3052f54902793cae02a3aedfb1040c7c487e1352b698c4914d85fc

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for ecobee-home (2 malicious versions).

  2. If you installed it — respond

    ecobee-home is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If ecobee-home was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ecobee-home on npm has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018693GHSA-fhh5-9f4g-qw3hIN-MAL-2026-019780

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ecobee-home-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

ecobee-home (npm) malicious package — MAL-2026-14475 | O3 Security