Which versions of thread_ppe-test are malicious?

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

How do I remediate thread_ppe-test if I installed it?

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

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

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

Search your lockfiles and build artifacts for thread_ppe-test (version 1.0.0).

Malicious package

thread_ppe-testnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

thread_ppe-test is a confirmed malicious npm package (MAL-2026-1867) 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 thread_ppe-test (npm)

MAL-2026-1867

Immediate action

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

npm uninstall thread_ppe-test

What this malware does

The package thread_ppe-test was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bcdda6bf761bf26ea5d47f15cc283a9dcd197c36cfe4b5d27a40c8091cc476ea

94a9d2420c318197cca9d0d4523f1049462bd1abfbe0288f9679074611434235

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for thread_ppe-test (version 1.0.0).
If you installed it — respond
Remove thread_ppe-test 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 thread_ppe-test 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. thread_ppe-test 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-2026-01621

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks thread_ppe-test-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