Which versions of @liquid-web/utils are malicious?

The following npm versions of @liquid-web/utils are flagged malicious: 1.2.9213. Treat any of these as compromised.

How do I remediate @liquid-web/utils if I installed it?

Remove @liquid-web/utils 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 @liquid-web/utils — how do I know if it already compromised me?

If @liquid-web/utils 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 @liquid-web/utils part of a known attack campaign?

Yes — @liquid-web/utils is associated with the GHSA-5ph4-vqhq-9p2h, RLMA-2025-04848, RLUA-2026-01033 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 @liquid-web/utils 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 @liquid-web/utils (version 1.2.9213). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @liquid-web/utils across your stack and pipelines.

Malicious package

@liquid-web/utilsnpm

Malicious code in @liquid-web/utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47040

Immediate action

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

npm uninstall @liquid-web/utils

What this malware does

The package @liquid-web/utils was found to contain malicious code.

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

1 flagged

1.2.9213

Indicators of compromise (SHA-256)

02e29a386f30eacfd4a3e7023262f0bb759557fb0a41790632720ff54b920a8d

bd03072627871a18718a84b81e6d1587059c46d675a25f914e5e8554814d57f8

766c2605bcfaf6a3b7f4d3873843e24f1056b2108d8b0822adbbca7e18ce39a5

704a4294ec41eb3d2713b1f594b5f6ea3497318c2a7ee775517127c8141f9faa

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @liquid-web/utils (version 1.2.9213). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @liquid-web/utils across your stack and pipelines.
If you installed it — respond
Remove @liquid-web/utils 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 @liquid-web/utils 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 @liquid-web/utils 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. @liquid-web/utils on npm has been identified as a malicious package (version 1.2.9213 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5ph4-vqhq-9p2hRLMA-2025-04848RLUA-2026-01033

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @liquid-web/utils-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