Which versions of boxy-fixture-paperclip are malicious?

The following npm versions of boxy-fixture-paperclip are flagged malicious: 35.8.2. Treat any of these as compromised.

How do I remediate boxy-fixture-paperclip if I installed it?

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

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

Yes — boxy-fixture-paperclip is associated with the IN-MAL-2026-015334 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 boxy-fixture-paperclip 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 boxy-fixture-paperclip (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-fixture-paperclip across your stack and pipelines.

Malicious package

boxy-fixture-paperclipnpm

boxy-fixture-paperclip is a confirmed malicious npm package (MAL-2026-13045) that executes malicious code on install (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-fixture-paperclip (npm)

MAL-2026-13045

Immediate action

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

npm uninstall boxy-fixture-paperclip

What this malware does

On any require/import, index.js loads _adapter.js, which selects a platform-specific asset and downloads an opaque binary from a rotating set of Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev). The hostnames are reassembled at runtime via array-join to defeat static string extraction. The downloaded bytes are written to a hidden dot-file under /var/tmp (POSIX) or %TEMP% (Windows), chmod 0755'd, and executed detached via spawn('/bin/sh', ['-c',...]) or spawn('cmd',...). A DNS-TXT covert channel under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru provides a fallback that chunk-reassembles a base64 payload from TXT records when the primary hosts are unreachable. The tarball also ships lib/telemetry.js, an ~81 KB parallel dropper module masquerading as a Sentry-like analytics SDK that is not referenced in this version but duplicates the _adapter.js payload-staging shape. Installing or importing this package results in execution of attacker-controlled code on the installer's machine.

Malicious versions

1 flagged

35.8.2

Indicators of compromise (SHA-256)

78a47f722fb30af7936e07182fa5fb42ecfd7efbacadd970a148a8a7daefc8e2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-fixture-paperclip (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-fixture-paperclip across your stack and pipelines.
If you installed it — respond
Remove boxy-fixture-paperclip 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 boxy-fixture-paperclip 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 boxy-fixture-paperclip 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. boxy-fixture-paperclip on npm has been identified as a malicious package (version 35.8.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015334

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-fixture-paperclip-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