Which versions of pentestlyio-testpackage are malicious?

The following npm versions of pentestlyio-testpackage are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate pentestlyio-testpackage if I installed it?

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

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

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

Search your lockfiles and build artifacts for pentestlyio-testpackage (2 malicious versions).

Malicious package

pentestlyio-testpackagenpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

pentestlyio-testpackage is a confirmed malicious npm package (MAL-2025-192850) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pentestlyio-testpackage (npm)

MAL-2025-192850

Immediate action

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

npm uninstall pentestlyio-testpackage

What this malware does

The package pentestlyio-testpackage was found to contain malicious code.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

5dc6e3e6722638b89ab41908c0a9641369b5b42b0b0523c356d28a842b1af2e5

c33a99a3bfd88931eb474977950169e0ee173b9f3df727cdcec54ec1fd3b1ed3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06446

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pentestlyio-testpackage-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