Which versions of @youcanneverguessthisonereally/test-pkg are malicious?

The following npm versions of @youcanneverguessthisonereally/test-pkg are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @youcanneverguessthisonereally/test-pkg if I installed it?

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

If @youcanneverguessthisonereally/test-pkg 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 @youcanneverguessthisonereally/test-pkg part of a known attack campaign?

Yes — @youcanneverguessthisonereally/test-pkg is associated with the RLMA-2026-01871 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 @youcanneverguessthisonereally/test-pkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @youcanneverguessthisonereally/test-pkg (version 1.0.0).

Malicious package

@youcanneverguessthisonereally/test-pkgnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

@youcanneverguessthisonereally/test-pkg is a confirmed malicious npm package (MAL-2026-2719) 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 @youcanneverguessthisonereally/test-pkg (npm)

MAL-2026-2719

Immediate action

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

npm uninstall @youcanneverguessthisonereally/test-pkg

What this malware does

The package @youcanneverguessthisonereally/test-pkg was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3ac6a911aacd0a2e6f13a1c93055590ef4297fe6780f5e9e1fd0c78ed5ba4360

aee30c3c314a7edd599cfa020d43c4fdc7dec927af6e0af8a7772a3b25d8b63c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @youcanneverguessthisonereally/test-pkg (version 1.0.0).
If you installed it — respond
Remove @youcanneverguessthisonereally/test-pkg 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 @youcanneverguessthisonereally/test-pkg 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. @youcanneverguessthisonereally/test-pkg 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-01871

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @youcanneverguessthisonereally/test-pkg-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