What does the boxy-fixture-allure malware do?

boxy-fixture-allure ships an index.js that unconditionally requires./_shim on load. _shim.js reconstructs C2 hostnames via runtime string-splitting/.join() over fragments (assembling *.workers.dev CDN endpoints and a DNS TXT-record fallback under *.well1.site), fetches a platform-specific native binary, writes it to /var/tmp/.cache_ on Unix or %TEMP%\dotnet_diag_ .exe on Windows, chmods it 0o755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Payload naming (dotnet_diag,.cache_, analytics_state) and the presence of opt-out environment variable checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) serve as cover for the drop-and-execute behavior. The fetch fires

Which versions of boxy-fixture-allure are malicious?

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

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

boxy-fixture-allure is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed boxy-fixture-allure — how do I know if it already compromised me?

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

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

Malicious package

boxy-fixture-allurenpm

boxy-fixture-allure is a confirmed malicious npm package (MAL-2026-12342) that steals credentials and exfiltrates sensitive data (malicious version 20.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-fixture-allure (npm)

MAL-2026-12342

Immediate action

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

npm uninstall boxy-fixture-allure

What this malware does

boxy-fixture-allure ships an index.js that unconditionally requires./shim on load. shim.js reconstructs C2 hostnames via runtime string-splitting/.join() over fragments (assembling *.workers.dev CDN endpoints and a DNS TXT-record fallback under *.well1.site), fetches a platform-specific native binary, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag<hex>.exe on Windows, chmods it 0o755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Payload naming (dotnet_diag,.cache_, analytics_state) and the presence of opt-out environment variable checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) serve as cover for the drop-and-execute behavior. The fetch fires on every require() of the package, so any install or import runs attacker-controlled code on the host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

20.8.1

Indicators of compromise (SHA-256)

ef7772152485e16aab94cf983bcc5470787d75d67bb58b6f9fd8e44e1497fcbc

8c900b94efc137cab350c98b3fed461c9b172e9bda43ff02312f879c3f24bc71

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-fixture-allure (version 20.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-fixture-allure across your stack and pipelines.
If you installed it — respond
boxy-fixture-allure is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If boxy-fixture-allure 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-allure 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-allure on npm has been identified as a malicious package (version 20.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014689GHSA-cq8x-34cv-8xxm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-fixture-allure-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database