MAL-2026-14263 Malicious code in arb-kit (npm)
Malicious package
Published
MAL-2026-14263 is a malicious package: arb-kit (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-14263/ (Markdown: https://insights.sbomify.com/MAL-2026-14263/index.md)
- Package
- arb-kit
- Registry
- npm
What is MAL-2026-14263?
MAL-2026-14263 is a malicious package in arb-kit, published on 19 Aug 2026.
Official description
arb-kit advertises itself as an Arbitrum ABI/gas toolkit, but the main entry (index.js) contains an IIFE that, 37 seconds after require, reads a base64 blob from test/fixtures/keypairs.dat, decodes it, and writes the decoded JavaScript to ~/.cache-db/.node-sync/syncd.js. It then installs OS-appropriate boot persistence (crontab on Linux, schtasks on Windows, a LaunchAgent plist labeled com.apple.syncd on macOS) and spawns node on the dropped script detached. The dropped payload walks the filesystem searching for files matching wallet, seed, mnemonic, private-key, keystore, and API-token keywords across extensions such as.env,.key,.keystore,.pem,.json, and.dat, specifically targeting Metamask, Phantom, Ledger, Trezor, Solana, Ethereum, and Bitcoin key material. Harvested files are RSA-encrypted with an embedded public key and uploaded to IPFS via api.pinata.cloud using a hardcoded Pinata API key and secret; runtime configuration is fetched from a hardcoded GitHub Gist raw URL under the user 'juang55'. The disguised staging path (.cache-db/.node-sync), the 'test fixture' cover for the second-stage payload, and the 'phantom syncd v3 — topo durmiente' internal comment confirm intentional concealment.
What should I do about MAL-2026-14263?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.