Which versions of binproto are malicious?

The following npm versions of binproto are flagged malicious: 1.0.5, 1.0.7. Treat any of these as compromised.

How do I remediate binproto if I installed it?

Remove binproto 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is binproto part of a known attack campaign?

Yes — binproto is associated with the IN-MAL-2026-006828, IN-MAL-2026-006829 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect binproto in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking binproto and packages like it before any post-install script runs.

Malicious package

binprotonpm

Malicious code in binproto (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5924

Immediate action

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

npm uninstall binproto

What this malware does

On any call to the exported pack() function, index.js downloads a platform-specific binary from https://wotann-dktl.vercel.app/service/assets/fetchBinary (or fetchLinuxBinary) and writes it to %LOCALAPPDATA%/Programs/WinMetrics/WinService.exe on Windows or ~/.local/share/WinMetrics/WinMetrics on Linux. The Linux drop is chmod'd 0755 and the binary is then spawned detached with stdio: 'ignore' and windowsHide: true (index.js:67), unref'd so it survives the parent process. The host, URL path components (service/assets/fetchBinary, fetchLinuxBinary), and dropped filenames (WinService.exe, WinMetrics) are assembled at runtime from String.fromCharCode numeric arrays (index.js:23-28,:49) to hide them from scanners. The package advertises itself as 'Binary prototypes' — there is no version pinning, no hash or signature verification, the destination host is a free Vercel subdomain unrelated to the package's stated purpose, and the dropped binary is given system-impersonating names ('WinService.exe' under 'Programs/WinMetrics') to blend into process lists. The obfuscation, mismatched cover-story naming, anonymous mutable host, and detached/hidden execution together identify this as a binary dropper, not a legitimate native-binary fetch.

Malicious versions

2 flagged

1.0.51.0.7

Indicators of compromise (SHA-256)

1bbe88a299e58c31b71b346733abb6684ce1a1e8e68fad118eca48a53a2b15a3

472099c9263e5c2592d818a4068a978079a3f77a26edcf855cb19e06947d7aee

Frequently asked questions

No. binproto on npm has been identified as a malicious package (versions 1.0.5, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006828IN-MAL-2026-006829

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection