Which versions of puzzle-fragment are malicious?

The following npm versions of puzzle-fragment are flagged malicious: 1.3.1. Treat any of these as compromised.

How do I remediate puzzle-fragment if I installed it?

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

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

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

Search your lockfiles and build artifacts for puzzle-fragment (version 1.3.1).

Malicious package

puzzle-fragmentnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in puzzle-fragment (npm)

MAL-2026-2794

Immediate action

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

npm uninstall puzzle-fragment

What this malware does

The package puzzle-fragment was found to contain malicious code.

Malicious versions

1 flagged

1.3.1

Indicators of compromise (SHA-256)

be573b6cd2c3e20b069e964416370977f4513fe616fe10369bd66bc6a841bc78

ad106eae22a8aa21a17cd44167776eebe2a94c245f6e224ba0d52312d8dd229c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02027

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks puzzle-fragment-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