Is @duckdb/node-api safe?

The DuckDB Node.js package @duckdb/node-api version 1.3.3 was compromised with malware through a sophisticated phishing attack targeting the DuckDB maintainers. An attacker created a pixel-perfect copy of the npmjs.com website at npmjs.help domain and tricked a maintainer into logging in and resetting 2FA. The attacker then used stolen credentials to publish malicious versions of DuckDB packages. The malicious code was designed to interfere with cryptocurrency transactions, potentially allowing the attacker to steal or manipulate crypto wallet addresses and transactions. This represents a supply chain attack where legitimate packages were compromised to distribute malware. The attack was discovered within 4 hours and the affected versions were immediately deprecated and deleted from npm. The maintainers re-released safe versions (1.3.4) to ensure users get clean packages.

Malicious

1.3.3

Move to

1.5.6-r.2 newest 1.x release, no known advisory

2.0.0-r.1 current release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @duckdb/node-api@1.5.6-r.2

OSV recordadvisory