Which versions of portal-aes are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for portal-aes (version 1.3.3).

Malicious package

portal-aesnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

portal-aes is a confirmed malicious npm package (MAL-2025-192853) that executes malicious code on install (malicious version 1.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in portal-aes (npm)

MAL-2025-192853

Immediate action

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

npm uninstall portal-aes

What this malware does

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

Malicious versions

1 flagged

1.3.3

Indicators of compromise (SHA-256)

933808e340ae94342446f733f8873878bddd9a18b39ec841be7027f659fbb0c9

dcd7acb81f0b0d24b59d66c6eecaec74aeb0a5ac6c9a1a3a37a5d3dd7f962bdf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06451

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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