Which versions of homekit-mcp are malicious?

The following npm versions of homekit-mcp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate homekit-mcp if I installed it?

homekit-mcp 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.

I already installed homekit-mcp — how do I know if it already compromised me?

If homekit-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is homekit-mcp part of a known attack campaign?

Yes — homekit-mcp is associated with the IN-MAL-2026-018415 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 homekit-mcp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for homekit-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging homekit-mcp across your stack and pipelines.

Malicious package

homekit-mcpnpm

homekit-mcp is a confirmed malicious npm package (MAL-2026-14297) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in homekit-mcp (npm)

MAL-2026-14297

Immediate action

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

npm uninstall homekit-mcp

What this malware does

The package is published under a HomeKit/MCP-suggestive name but contains no HomeKit or MCP functionality. lib/report.js resolves the installer's email via gh api user/emails, git config user.email, ~/.gitconfig, ~/.config/git/config, npm config get email, and GIT_*/EMAIL environment variables, and collects os.hostname() and os.userInfo().username. It then POSTs {email, username, hostname, run_count, package_name} to a hardcoded Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. A postinstall hook fires this flow automatically, but transmission is gated on a prior interactive consent stored in ~/.install-email-research.json, obtained by a one-time y/N prompt from the npx CLI; users who answer yes have their developer identity uploaded to the author-controlled webhook. package.json self-describes the code as a 'harmless security research payload' by 'Capsule Security', and the package name is unrelated to the actual behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8aae79beeec5e53410060b09eae14979ac2c1f27c62da6b750a612651f8ea8fe

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for homekit-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging homekit-mcp across your stack and pipelines.
If you installed it — respond
homekit-mcp 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.
Did it already run?
If homekit-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks homekit-mcp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. homekit-mcp on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018415

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database