Which versions of pil2-stark-js are malicious?

The following npm versions of pil2-stark-js are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate pil2-stark-js if I installed it?

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

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

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

Search your lockfiles and build artifacts for pil2-stark-js (version 99.0.1).

Malicious package

pil2-stark-jsnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

pil2-stark-js is a confirmed malicious npm package (MAL-2026-2793) that executes malicious code on install (malicious version 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pil2-stark-js (npm)

MAL-2026-2793

Immediate action

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

npm uninstall pil2-stark-js

What this malware does

The package pil2-stark-js was found to contain malicious code.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

054292b5f67a703e53444e254f5ef9f7b268b8c4173e987f443afd97c98d0a97

d38245d3114b579956426c150e00f8821821c418e0d87077788d0180ed19a054

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02021

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pil2-stark-js-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