Which versions of nileninjapkg5 are malicious?

The following npm versions of nileninjapkg5 are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate nileninjapkg5 if I installed it?

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

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

Yes — nileninjapkg5 is associated with the RLMA-2025-05439, RLUA-2026-01454 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 nileninjapkg5 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nileninjapkg5 (2 malicious versions).

Malicious package

nileninjapkg5npm

Advisory published Oct 6, 2025Updated Mar 19, 2026

nileninjapkg5 is a confirmed malicious npm package (MAL-2025-48374) that executes malicious code on install (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nileninjapkg5 (npm)

MAL-2025-48374

Immediate action

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

npm uninstall nileninjapkg5

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

cf4d0345303a2c0525ecc8bd1b2a1e3d30efbaf6c87609a970faf16e246f1ad9

855b999555760e8533cff916b9c19ad6309a5b7e11f3f892dda932d5d29044fd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05439RLUA-2026-01454

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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