Which versions of web-uj65mn are malicious?

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

How do I remediate web-uj65mn if I installed it?

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

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

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

Search your lockfiles and build artifacts for web-uj65mn (version 1.0.0).

Malicious package

web-uj65mnnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

web-uj65mn is a confirmed malicious npm package (MAL-2025-191602) 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 web-uj65mn (npm)

MAL-2025-191602

Immediate action

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

npm uninstall web-uj65mn

What this malware does

The package web-uj65mn was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

df1516a455b68ae474da795fd13367d90ccb8223cedc0722f8a0e3c3305edc75

e56dbe5adc231ec457351fe336d2bcdd18f99b4c582b0e08e072df28d9f87bc8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for web-uj65mn (version 1.0.0).
If you installed it — respond
Remove web-uj65mn 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 web-uj65mn 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. web-uj65mn 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-2025-06000

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks web-uj65mn-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