Which versions of boxy-service are malicious?

The following npm versions of boxy-service are flagged malicious: 35.6.4. Treat any of these as compromised.

How do I remediate boxy-service if I installed it?

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

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

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

Malicious package

boxy-servicenpm

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

Malicious code in boxy-service (npm)

MAL-2026-13082

Immediate action

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

npm uninstall boxy-service

What this malware does

On require of the package, index.js unconditionally loads compat.js, which reconstructs attacker-controlled hostnames from split string arrays (oob-worker.cf10[0-3]-*.workers.dev and sdk.dl.wel1.ru), selects a per-OS endpoint, and downloads a platform-specific binary from paths such as /pkg/package, /pkg/loader_mac, and /pkg/package.exe. The binary is written to a hidden path (/tmp/.cache<rand> on Unix, %TEMP%/dotnet_diag_<rand>.exe on Windows under a.NET diagnostics cover name), chmod 0755'd on Unix, and detached-spawned via /bin/sh -c or cmd.exe /c start. A secondary covert channel resolves DNS TXT records for numbered subdomains under sdk.dl.wel1.ru, concatenates the responses, base64-decodes them, and treats the result as an executable payload. A second loader with the same shape is present in lib/telemetry.js under an 'Analytics SDK' cover story, using split identifiers such as require('child_'+'process') and fs['chmod'+'Sync'] to evade static inspection. The package uses hidden filenames, dot-prefixed paths, cover names imitating Microsoft diagnostics, string-array host reassembly, and DNS-TXT payload staging to conceal both the destinations and the behavior.

Malicious versions

1 flagged

35.6.4

Indicators of compromise (SHA-256)

4ecbc929cc9a3cab12301c7879112bd95abb78812a0248415cc4f7c075d3eec1

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

Campaign

IN-MAL-2026-015293

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-service-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