Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@liquid-web/app-servicesnpm

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

MAL-2025-47032
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @liquid-web/app-services

What this malware does

The package @liquid-web/app-services 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)

d2360336c035ddfac0df30665d2e803482a726fbf6c47738903b8d3b7eb6c248
d7be0210df64d58752ddf05395291687734e14cf237c710125ac49d3cb3f68d9
c910252a385c36277fec8f1143a453ce70185c7d3ce3830ec384e4d013526254
11921b2f3def64d2773d068d962b0517ac4754235004ba9bc286c6e1ecd94fd9

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @liquid-web/app-services (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/app-services across your stack and pipelines.

  2. If you installed it — respond

    Remove @liquid-web/app-services 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.

  3. Did it already run?

    If @liquid-web/app-services 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.

  4. How O3 protects you

    O3 blocks @liquid-web/app-services 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/app-services 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-jr76-8rr5-qfxjRLMA-2025-04840RLUA-2026-01025

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @liquid-web/app-services-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.