Which versions of liportal-web-app are malicious?

The following npm versions of liportal-web-app are flagged malicious: 99.1.9, 99.9.9. Treat any of these as compromised.

How do I remediate liportal-web-app if I installed it?

Remove liportal-web-app 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 liportal-web-app — how do I know if it already compromised me?

If liportal-web-app 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 liportal-web-app part of a known attack campaign?

Yes — liportal-web-app is associated with the RLMA-2026-05142, RLUA-2026-06308 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 liportal-web-app across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for liportal-web-app (2 malicious versions).

Malicious package

liportal-web-appnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

liportal-web-app is a confirmed malicious npm package (MAL-2026-7313) that executes malicious code on install (malicious versions 99.1.9, 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in liportal-web-app (npm)

MAL-2026-7313

Immediate action

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

npm uninstall liportal-web-app

Malicious versions

2 flagged

99.1.999.9.9

Indicators of compromise (SHA-256)

9835c5597fa88a7cb2b44ca45651b986e31da8d2d2bee0a588a999975744f990

21d69c8de12cf04de136d3a7e0577f3d67ea39b4d0e04df45eb555628257fbc6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for liportal-web-app (2 malicious versions).
If you installed it — respond
Remove liportal-web-app 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 liportal-web-app 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. liportal-web-app on npm has been identified as a malicious package (versions 99.1.9, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05142RLUA-2026-06308

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks liportal-web-app-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