Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

boxy-mmb-deps-pvm-pluginnpm

boxy-mmb-deps-pvm-plugin is a confirmed malicious npm package (MAL-2026-13071) that executes malicious code on install (malicious version 35.6.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-mmb-deps-pvm-plugin (npm)

MAL-2026-13071
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-mmb-deps-pvm-plugin

What this malware does

index.js unconditionally loads polyfill.js on require. polyfill.js reconstructs attacker-controlled hostnames from split string literals (oob-worker.cf101-adf.workers.dev, cf102-baf.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev), downloads a platform-specific binary via https.get, and — if HTTPS fails — falls back to a DNS TXT covert channel that reassembles base64-chunked payload bytes from c.<domain> and <i>.<domain> lookups against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd /c start. lib/telemetry.js ships a second copy of the same dropper under an 'analytics-sdk' cover story, loading child_process through require("child_"+"process") and calling fs["chmod"+"Sync"] to further hide the pattern. The package's stated 'plugin' purpose does not match the shipped payload-delivery infrastructure.

Malicious versions

1 flagged
35.6.5

Indicators of compromise (SHA-256)

088639f9b19ce8234cef116c0250628c6894bd509915aa90639c56436ec19646

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-mmb-deps-pvm-plugin (version 35.6.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-mmb-deps-pvm-plugin across your stack and pipelines.

  2. If you installed it — respond

    Remove boxy-mmb-deps-pvm-plugin 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-mmb-deps-pvm-plugin 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.

  4. How O3 protects you

    O3 blocks boxy-mmb-deps-pvm-plugin 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-mmb-deps-pvm-plugin on npm has been identified as a malicious package (version 35.6.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015306

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-mmb-deps-pvm-plugin-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
boxy-mmb-deps-pvm-plugin (npm) malicious package — MAL-2026-13071 | O3 Security