Which versions of ranko887 are malicious?

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

How do I remediate ranko887 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ranko887 (3 malicious versions).

Malicious package

ranko887npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in ranko887 (npm)

MAL-2026-1832

Immediate action

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

npm uninstall ranko887

What this malware does

The package ranko887 was found to contain malicious code.

Malicious versions

3 flagged

1.0.01.0.11.0.4

Indicators of compromise (SHA-256)

80da520c11d7d24e95db22e3a6c7e2532ac387f506490eca6803a2012f14f33a

43ccc3824edef6d50613c4b4b27c79676ff219a2ce6741185045e6ccc85d31e2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01519

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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