What does the boxy-pkg-path malware do?

index.js unconditionally loads _support.js on require. _support.js reconstructs Cloudflare Workers hostnames (oob-worker.cf10{0,1,2}-*.workers.dev) and a.ru DNS-TXT fallback (*.dl.wel1.ru) from string-split character fragments, downloads a platform-specific binary via https.get, writes it to a masqueraded path (/tmp/.cache_ on Unix or %TEMP%\dotnet_diag_ .exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Deceptive comments frame the endpoints as CDN/IPv4 SDK behavior, and a TTL marker prevents repeat execution. lib/telemetry.js, presented as an 'Analytics SDK', contains a parallel implementation of the same dropper primitives (base64-chunked payload deco

Which versions of boxy-pkg-path are malicious?

The following npm versions of boxy-pkg-path are flagged malicious: 35.3.5. Treat any of these as compromised.

How do I remediate boxy-pkg-path if I installed it?

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

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

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

Malicious package

boxy-pkg-pathnpm

boxy-pkg-path is a confirmed malicious npm package (MAL-2026-13076) that executes malicious code on install (malicious version 35.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-pkg-path (npm)

MAL-2026-13076

Immediate action

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

npm uninstall boxy-pkg-path

What this malware does

index.js unconditionally loads support.js on require. support.js reconstructs Cloudflare Workers hostnames (oob-worker.cf10{0,1,2}-.workers.dev) and a.ru DNS-TXT fallback (.dl.wel1.ru) from string-split character fragments, downloads a platform-specific binary via https.get, writes it to a masqueraded path (/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Deceptive comments frame the endpoints as CDN/IPv4 SDK behavior, and a TTL marker prevents repeat execution. lib/telemetry.js, presented as an 'Analytics SDK', contains a parallel implementation of the same dropper primitives (base64-chunked payload decode, chmodSync 0755, /bin/sh spawn of the written file) as an alternate payload path. Any require('boxy-pkg-path') results in arbitrary attacker-controlled code executing on the installer's host.

Malicious versions

1 flagged

35.3.5

Indicators of compromise (SHA-256)

ae99d3d2f9b6c2a5a47e8edd34fb78968ffc58c3a514e04ad10b14455d7436f2

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-pkg-path (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-pkg-path across your stack and pipelines.
If you installed it — respond
Remove boxy-pkg-path 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-pkg-path 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-pkg-path 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-pkg-path on npm has been identified as a malicious package (version 35.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015302

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-pkg-path-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