Which versions of tierlist are malicious?

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

How do I remediate tierlist if I installed it?

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

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

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

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

Malicious package

tierlistnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

tierlist is a confirmed malicious npm package (MAL-2025-192880) 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 tierlist (npm)

MAL-2025-192880

Immediate action

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

npm uninstall tierlist

What this malware does

The package tierlist was found to contain malicious code.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

9ec60cbc97b2d578bce42520ac7d8a845789197224617abe6b807dde35ebca10

e8c0d7aec1c2dad0a73d9953a06b4dd7ec870e6e8702bfa608262598277edbfd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06518

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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