Which versions of urti are malicious?

The following npm versions of urti are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate urti if I installed it?

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

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

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

Search your lockfiles and build artifacts for urti (4 malicious versions).

Malicious package

urtinpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

urti is a confirmed malicious npm package (MAL-2026-1871) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in urti (npm)

MAL-2026-1871

Immediate action

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

npm uninstall urti

What this malware does

The package urti was found to contain malicious code.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.4

Indicators of compromise (SHA-256)

9b16ead04d163afb85def5de3a48faab5eec352f56a9731c25f745436ce875f0

ce210748591c19c8937ecaf130c45acf772c6e762dc06ce07f48d5d8d512c451

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01635

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks urti-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