Which versions of paperclip2 are malicious?

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

How do I remediate paperclip2 if I installed it?

paperclip2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed paperclip2 — how do I know if it already compromised me?

If paperclip2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is paperclip2 part of a known attack campaign?

Yes — paperclip2 is associated with the IN-MAL-2026-007954 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 paperclip2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paperclip2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paperclip2 across your stack and pipelines.

Malicious package

paperclip2npm

Malicious code in paperclip2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6755

Immediate action

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

npm uninstall paperclip2

What this malware does

package.json declares a postinstall lifecycle script that runs node -e code opening a TCP connection to 185.112.147.174:7007 and piping the socket to a spawned /bin/sh, giving the operator of that endpoint an interactive shell on the installer's machine. The package ships no other functionality — its sole effect on install is to establish this reverse shell. Any developer workstation or CI job running npm install paperclip2 is compromised with arbitrary code execution as the invoking user.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b6fbcfc445b1a599943dac3ca0691633629c6804037b38fcf6113062f6add848

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paperclip2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paperclip2 across your stack and pipelines.
If you installed it — respond
paperclip2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If paperclip2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks paperclip2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. paperclip2 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

IN-MAL-2026-007954

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks paperclip2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring