boardflownpm
boardflow is a confirmed malicious npm package (MAL-2026-5799) that executes malicious code on install (malicious versions 1.1.4, 1.1.5, 1.1.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boardflow (npm)
What this malware does
package.json declares preinstall: node install.js, which fires automatically on npm install. install.js is heavily obfuscated (obfuscator.io string-array shuffle with _0xNNNN identifiers and split-string concatenation) to hide its behavior. After deobfuscation, the script downloads https://www.pooron.org/ice.exe into the OS temp directory as tester_<randomhex>.exe, chmods it 755, and spawn-detaches it via spawn(PAYLOAD_PATH, [], {detached:true, stdio:'ignore', windowsHide:true}).unref() — using a cmd-style invocation on Windows and direct exec on macOS/Linux. A console message [boardstep] Optional dependency initialized. is printed as a cover story (note that boardstep does not match the package name boardflow). The payload domain pooron.org is not the package's publisher, the URL is mutable and unpinned, no hash or signature check is performed, and the binary is opaque. Supporting indicators of disposability: README is 0 bytes, dependencies declares a self-reference (boardflow: ^1.1.8), and the package's stated kanban purpose has no implementing code. This is a textbook install-time dropper: any developer or build system running npm install boardflow immediately executes attacker-controlled code with the installer's privileges.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boardflow (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boardflow across your stack and pipelines.
If you installed it — respond
Remove boardflow 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.
Did it already run?
If boardflow 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 boardflow 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks boardflow-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.