new-native-tools-linux-x64-gnunpm
new-native-tools-linux-x64-gnu is a confirmed malicious npm package (MAL-2026-12402) that steals credentials and exfiltrates sensitive data (malicious versions 3.1.40-as2-9923-378-1785154830, 3.1.40-browser-release-151-380-1785161758, 3.1.41-origin-chrom-468-delete-windows-32-bit-changelog-fix-408-1785838091). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in new-native-tools-linux-x64-gnu (npm)
What this malware does
The package's only shipped artifact is a 10 MB Linux x86_64 ELF Node addon set as main (tools.linux-x64-gnu.node), so it is loaded automatically on require(). Extracted strings from the binary contain the exact Chromium Cookies SQLite schema (FROM cookies, DROP INDEX IF EXISTS cookies_unique_index, CREATE UNIQUE INDEX cookies_unique_index ON cookies(host_key, top_frame_site_key,...)) and password-store log lines (Found login for, failed to read:), consistent with reading Chromium/Chrome/Chromium-derivative Cookies and Login Data stores on the installer host. The same binary embeds a full outbound HTTPS stack (rustls, hyper/ureq) with proxy-environment support (HTTPS_PROXY, HTTP_PROXY, ALL_PROXY) and host-fingerprinting primitives (gethostname, getifaddrs, /etc/lsb-release, /dev/disk/by-id/, CPU info, network_adapters), plus ZIP + zstd packaging routines suitable for bundling collected data before upload. The exfiltration destination is not present as a plain string and is reconstructed at runtime. Package name mimics the @napi-rs/* / @next/swc-* platform-binary convention; the README states only "the x86_64-unknown-linux-gnu binary for new-native-tools" and does not disclose any browser-data access or network activity. The version tag 3.1.40-browser-release-151-380-1785161758 includes a unix-epoch-like suffix consistent with automated mass-publication.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for new-native-tools-linux-x64-gnu (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-native-tools-linux-x64-gnu across your stack and pipelines.
If you installed it — respond
new-native-tools-linux-x64-gnu is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If new-native-tools-linux-x64-gnu 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 new-native-tools-linux-x64-gnu 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 new-native-tools-linux-x64-gnu-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.