Which versions of outer-package are malicious?

The following npm versions of outer-package are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate outer-package if I installed it?

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

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

Yes — outer-package is associated with the RLMA-2026-05198, RLUA-2026-06359 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 outer-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for outer-package (version 1.0.0).

Malicious package

outer-packagenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in outer-package (npm)

MAL-2026-7334

Immediate action

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

npm uninstall outer-package

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

07b6e797e44b6a7b015d75fe9333b48b2dab491548ef206eec77a11cd9ef4a17

965dbe87de1cec55f029441c4a68deec79aad96a985faf70701fd86be92f80eb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05198RLUA-2026-06359

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks outer-package-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