Which versions of ecobee2 are malicious?

The following npm versions of ecobee2 are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate ecobee2 if I installed it?

ecobee2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ecobee2 — how do I know if it already compromised me?

If ecobee2 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.

Is ecobee2 part of a known attack campaign?

Yes — ecobee2 is associated with the IN-MAL-2026-018690, GHSA-339h-mj38-2p38, IN-MAL-2026-019782 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ecobee2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ecobee2 (2 malicious versions).

Malicious package

ecobee2npm

Advisory published Aug 25, 2026Updated Sep 9, 2026

ecobee2 is a confirmed malicious npm package (MAL-2026-14476) that opens a backdoor for remote access (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecobee2 (npm)

MAL-2026-14476

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ecobee2

What this malware does

package.json declares scripts.postinstall = 'node beacon.js', which runs automatically on npm install. beacon.js performs an HTTP GET to http://169.58.96.170:9001/cb with the installer's os.hostname() and the package name in the query string, disclosing host identity to a hardcoded bare-IP endpoint over cleartext HTTP at install time. The package README is a placeholder and no legitimate purpose is documented for this network activity.

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)

42ebdeda4d4d0b3db14833d23a2d75a55e7e3f6af902f0ba6f545a970c0f09ba

433e6da70dcc00a79a94af9cb397f0bf739fddf3f9e8b435734831e2adc83781

d4305a47de47cf32d81a8c4d614393ed8b9247fe6254487819f2467da6412b38

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for ecobee2 (2 malicious versions).
If you installed it — respond
ecobee2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ecobee2 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. ecobee2 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-018690GHSA-339h-mj38-2p38IN-MAL-2026-019782

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ecobee2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database