Which versions of testctfproject2 are malicious?

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

How do I remediate testctfproject2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for testctfproject2 (2 malicious versions).

Malicious package

testctfproject2npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

testctfproject2 is a confirmed malicious npm package (MAL-2026-1865) that executes malicious code on install (malicious versions 0.30.1, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testctfproject2 (npm)

MAL-2026-1865

Immediate action

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

npm uninstall testctfproject2

What this malware does

The package testctfproject2 was found to contain malicious code.

Malicious versions

2 flagged

0.30.11.0.0

Indicators of compromise (SHA-256)

9b65c3ba65d23b030c42073e2177248726cbea161359169d50be1b349dac2363

b6213fefa0d02cebbb70d11d3c2f97eb314aaa7277cdf97dd1bcdb088e037538

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01619

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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