NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

boxy-test-block-fixturenpm

Advisory published Updated

boxy-test-block-fixture is a confirmed malicious npm package (MAL-2026-13089) that executes malicious code on install (malicious version 35.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-test-block-fixture (npm)

MAL-2026-13089
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-test-block-fixture

What this malware does

On require()/import of the package, init.js assembles attacker-controlled hostnames at runtime by joining split string fragments (resolving to oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), fetches a platform-specific binary over HTTPS, and if that fails, falls back to a DNS-TXT covert channel that reassembles base64-encoded payload chunks from subdomains of dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under cover-story names such as 'dotnet_diag.exe' and '.cache_', chmod 0755, and executed detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref() (or the cmd equivalent on Windows). No signature or hash verification is performed. The destination hostnames are obfuscated via array-join splitting to evade static string scans, and the DNS-TXT fallback bypasses HTTPS egress filtering. Any project that installs and loads this package executes attacker-controlled native code on the host.

Malicious versions

1 flagged
35.5.5

Indicators of compromise (SHA-256)

b10e5c9aa6fedcb9d29f292cd6f5aa6634e770f46c6385a9fb32c0fc628ab27a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for boxy-test-block-fixture (version 35.5.5).

  2. If you installed it — respond

    Remove boxy-test-block-fixture 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.

  3. Did it already run?

    If boxy-test-block-fixture was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. boxy-test-block-fixture on npm has been identified as a malicious package (version 35.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015299

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-test-block-fixture-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.

Explore

boxy-test-block-fixture (npm) malicious package — MAL-2026-13089 | O3 Security