Which versions of portal-lise are malicious?

The following npm versions of portal-lise are flagged malicious: 2.1.4. Treat any of these as compromised.

How do I remediate portal-lise if I installed it?

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

If portal-lise 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 portal-lise part of a known attack campaign?

Yes — portal-lise is associated with the GHSA-h847-vpq8-2hj8, RLMA-2026-01502 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 portal-lise 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 portal-lise (version 2.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging portal-lise across your stack and pipelines.

Malicious package

portal-lisenpm

Malicious code in portal-lise (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192970

Immediate action

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

npm uninstall portal-lise

What this malware does

The package portal-lise 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

2.1.4

Indicators of compromise (SHA-256)

6d0ea4511808b283817242b827687f9a2fb37a0a7f17db46db1f4acbd6ba0de8

cd0c023f6f7e2ba4df069103ad42d8cb03575410033a50f5887ec1d0fbe94205

c78c421948043c3286d6847cce918c63178c8faaeb45d01a14286cbd22d58f68

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 portal-lise (version 2.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging portal-lise across your stack and pipelines.
If you installed it — respond
Remove portal-lise 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 portal-lise 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 portal-lise 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. portal-lise on npm has been identified as a malicious package (version 2.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h847-vpq8-2hj8RLMA-2026-01502

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks portal-lise-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