Which versions of @housecallpro/marketing-site are malicious?

The following npm versions of @housecallpro/marketing-site are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @housecallpro/marketing-site if I installed it?

Remove @housecallpro/marketing-site 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 @housecallpro/marketing-site — how do I know if it already compromised me?

If @housecallpro/marketing-site 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 @housecallpro/marketing-site part of a known attack campaign?

Yes — @housecallpro/marketing-site is associated with the RLMA-2026-04737, RLUA-2026-05874 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 @housecallpro/marketing-site across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @housecallpro/marketing-site (version 0.0.1).

Malicious package

@housecallpro/marketing-sitenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@housecallpro/marketing-site is a confirmed malicious npm package (MAL-2026-7075) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @housecallpro/marketing-site (npm)

MAL-2026-7075

Immediate action

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

npm uninstall @housecallpro/marketing-site

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

38773474130c007509c82ebb7a863e0cad31d627d8b06b6da2c156e7ee624441

25557c8d5a926496d4171310bae46d7a74660c26410caef2b20bb5946eb0bb2b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @housecallpro/marketing-site (version 0.0.1).
If you installed it — respond
Remove @housecallpro/marketing-site 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 @housecallpro/marketing-site 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. @housecallpro/marketing-site on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04737RLUA-2026-05874

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @housecallpro/marketing-site-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