Which versions of @hsbc-mfe/host are malicious?

The following npm versions of @hsbc-mfe/host are flagged malicious: 99.99.3. Treat any of these as compromised.

How do I remediate @hsbc-mfe/host if I installed it?

Remove @hsbc-mfe/host 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 @hsbc-mfe/host — how do I know if it already compromised me?

If @hsbc-mfe/host 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 @hsbc-mfe/host part of a known attack campaign?

Yes — @hsbc-mfe/host is associated with the RLMA-2026-01702 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 @hsbc-mfe/host across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @hsbc-mfe/host (version 99.99.3).

Malicious package

@hsbc-mfe/hostnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

@hsbc-mfe/host is a confirmed malicious npm package (MAL-2026-2332) that executes malicious code on install (malicious version 99.99.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hsbc-mfe/host (npm)

MAL-2026-2332

Immediate action

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

npm uninstall @hsbc-mfe/host

What this malware does

The package @hsbc-mfe/host was found to contain malicious code.

Malicious versions

1 flagged

99.99.3

Indicators of compromise (SHA-256)

18226dfd197bfda21a7727cf606481ffea6e1b53a672de88f13dc8a5cde73696

8a848d447b30dd51c4c541fa6a6e6d377bfe77ee4b04b4904996f725b8519789

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01702

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @hsbc-mfe/host-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