boxy-fixture-pendelnpm
boxy-fixture-pendel is a confirmed malicious npm package (MAL-2026-13046) that executes malicious code on install (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-fixture-pendel (npm)
What this malware does
On require('boxy-fixture-pendel'), index.js loads support.js which asynchronously downloads a platform-specific binary from obfuscated destinations assembled at runtime via string-array.join('') — oob-worker.cf103-070.workers.dev and related Cloudflare Workers subdomains, with a DNS-TXT-record fallback channel that reassembles a base64-encoded binary from numbered TXT records under net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under cover-story filenames (dotnet_diag.exe,.cache_), chmod'd 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached: true}) or the Windows equivalent. There is no hash or signature verification, and the download destinations are unrelated to the package publisher. A second copy of the same dropper (split-concat hosts, /bin/sh -c spawn, chmod 0755, base64 buffer reassembly) is bundled in lib/telemetry.js under 'Analytics SDK' scaffolding; it is present in the tarball but not reached from index.js in this version. TTL caching and env-var opt-outs are included to reduce repeat triggering and aid evasion.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-fixture-pendel (version 35.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-fixture-pendel across your stack and pipelines.
If you installed it — respond
Remove boxy-fixture-pendel 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-pendel 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-pendel 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks boxy-fixture-pendel-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.