Which versions of resolve-uri-internal are malicious?

The following npm versions of resolve-uri-internal are flagged malicious: 99.1.0. Treat any of these as compromised.

How do I remediate resolve-uri-internal if I installed it?

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

If resolve-uri-internal 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 resolve-uri-internal part of a known attack campaign?

Yes — resolve-uri-internal is associated with the RLMA-2026-05279, RLUA-2026-06444 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 resolve-uri-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for resolve-uri-internal (version 99.1.0).

Malicious package

resolve-uri-internalnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

resolve-uri-internal is a confirmed malicious npm package (MAL-2026-7386) that executes malicious code on install (malicious version 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in resolve-uri-internal (npm)

MAL-2026-7386

Immediate action

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

npm uninstall resolve-uri-internal

Malicious versions

1 flagged

99.1.0

Indicators of compromise (SHA-256)

02f739bba45c540a1aadb2c716e6bbe3dc05d7a6110b99440df88ec19b5563ff

d8744eea8b11d5aa5b642d283e5ea20b897385c62e336e16e42d0920387cb590

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05279RLUA-2026-06444

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks resolve-uri-internal-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