Which versions of house-click are malicious?

The following npm versions of house-click are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate house-click if I installed it?

Remove house-click from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed house-click — how do I know if it already compromised me?

If house-click 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 house-click part of a known attack campaign?

Yes — house-click is associated with the RLMA-2026-01343 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 house-click across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for house-click (version 0.1.1).

Malicious package

house-clicknpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

house-click is a confirmed malicious npm package (MAL-2026-1744) that executes malicious code on install (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in house-click (npm)

MAL-2026-1744

Immediate action

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

npm uninstall house-click

What this malware does

The package house-click was found to contain malicious code.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

3799bf0926458dcccba257b74e10052c5f9cead5f017c0fbc2c74cf1f49f7ede

011a97ac4f78a9eb346b6a7fc5b087039824806b7cb064cceea2fc4c22b9d743

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for house-click (version 0.1.1).
If you installed it — respond
Remove house-click from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If house-click 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. house-click on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01343

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks house-click-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database