Which versions of portal-lime are malicious?

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

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

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

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

Yes — portal-lime is associated with the RLMA-2026-01501 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-lime across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for portal-lime (version 2.1.3).

Malicious package

portal-limenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

portal-lime is a confirmed malicious npm package (MAL-2026-1821) that executes malicious code on install (malicious version 2.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in portal-lime (npm)

MAL-2026-1821

Immediate action

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

npm uninstall portal-lime

What this malware does

The package portal-lime was found to contain malicious code.

Malicious versions

1 flagged

2.1.3

Indicators of compromise (SHA-256)

94381de623a657a017a0aad90e1c1b94f136b9eaa164e3a6f743263944139dd4

a61d5bfbd22f203a4a68f3329504312a967221d510ce7ceed02c663b0de8e002

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01501

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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