Which versions of testctfproject3 are malicious?

The following npm versions of testctfproject3 are flagged malicious: 0.30.1. Treat any of these as compromised.

How do I remediate testctfproject3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for testctfproject3 (version 0.30.1).

Malicious package

testctfproject3npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

testctfproject3 is a confirmed malicious npm package (MAL-2026-1866) that executes malicious code on install (malicious version 0.30.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testctfproject3 (npm)

MAL-2026-1866

Immediate action

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

npm uninstall testctfproject3

What this malware does

The package testctfproject3 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

f7120d5f44f56b959eb3bc39c0848b43943a66fae46fbd5236282b5d757699af

ac5d94cd8502eef9cfde3cf2cf891a6188172c6df1a8bcc20806c7ba15b7855d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01620

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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