@tuluax/errbnpm
@tuluax/errb is a confirmed malicious npm package (MAL-2026-11993) that typosquats a legitimate package to trick installs (malicious version 3.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @tuluax/errb (npm)
What this malware does
package.json scripts.install runs node -e "require('child_process').spawn('node', ['index.js'], { detached: true, stdio: 'ignore' }).unref()", causing npm install to spawn index.js as a detached background process. index.js reconstructs a network destination at runtime by AES-256-CBC-decrypting a hardcoded hex ciphertext with a hardcoded key and IV via createDecipheriv, then fetches the resulting URL and passes the response body to eval(). The endpoint controller therefore executes arbitrary JavaScript on the installer's machine at install time. The destination is hidden via cryptographic reconstruction rather than appearing as a plain string, defeating static URL scanning. The package impersonates the widely-used errno package by Rod Vagg: the tarball name is @tuluax/errb, package.json lists Rod Vagg @rvagg <[email protected]> as author despite publication under the unrelated @tuluax scope, and the README is titled node-errno and states Available in npm as errno.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tuluax/errb (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tuluax/errb across your stack and pipelines.
If you installed it — respond
@tuluax/errb is a typosquat — you almost certainly intended a legitimately-named package. Remove @tuluax/errb, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @tuluax/errb 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 @tuluax/errb 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 @tuluax/errb-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.