Which versions of boxy-mm-advisor are malicious?

The following npm versions of boxy-mm-advisor are flagged malicious: 35.3.2. Treat any of these as compromised.

How do I remediate boxy-mm-advisor if I installed it?

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

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

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

Malicious package

boxy-mm-advisornpm

boxy-mm-advisor is a confirmed malicious npm package (MAL-2026-13069) that opens a backdoor for remote access (malicious version 35.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-mm-advisor (npm)

MAL-2026-13069

Immediate action

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

npm uninstall boxy-mm-advisor

What this malware does

On require of boxy-mm-advisor, index.js loads init.js which auto-runs init(). The module reconstructs C2 hostnames via array-split-and-join obfuscation (yielding oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, and sdk/ext/pkg/net.dl.wel1.ru), selects a platform-specific payload URL, and fetches an unpinned unauthenticated binary via https.get. On POSIX it writes the bytes to /tmp/.cache<rand>, chmods 0755, and spawns '/bin/sh -c <file> &' detached; on Windows it writes to %TEMP%/dotnet_diag_<rand>.exe (impersonating a Microsoft diagnostic binary) and spawns via cmd.exe /c start /b detached. If HTTPS retrieval fails, dns.resolveTxt is used to read a chunk count from c.<domain>.dl.wel1.ru and to pull base64 chunks from 0.<domain>, 1.<domain>,..., which are concatenated, base64-decoded to a binary buffer, and executed identically. A.analytics_state marker suppresses re-triggering within ~6 hours. The package's advertised purpose is a trivial wrapper unrelated to fetching or executing native binaries.

Malicious versions

1 flagged

35.3.2

Indicators of compromise (SHA-256)

32b540f41a9d31185da353531b46adbb4d2bc9bd9b43efb79a4f8e80fbd51f8a

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

Campaign

IN-MAL-2026-015310

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-mm-advisor-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

Explore

All malware advisories How O3 detects malware Vulnerability database