Live data from Hacker News

Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

socket.dev

331–340 of 458 posts

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#331
post #278
post #51

https://github.com/doy/rbw is a Rust alternative to the Bitwarden CLI. Although the Rust ecosystem is moving in NPM's direction (very large and very deep dependency trees), you still need to trust far fewer authors in your dependency tree than what is common for Javascript.

I wonder if this is going to push more software to stacks like .Net where you can do most things with zero third-party dependencies. Or, conversely, encourage programming languages to increase the number of features in their standard libraries.

go and python exits with sane stdlib and are already used extensively

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#332

Anyone know of a better way to protect yourself than setting a min release age on npm/pnpm/yarn/bun/uv (and anything else that supports it)? Setting min-release-age=7 in .npmrc (needs npm 11.10+) would have protected the 334 unlucky people who downloaded the malicious @bitwarden/cli 2026.4.0, published ~19+ hours ago (see https://www.npmjs.com/package/@bitwarden/cli?activeTab=versi... and select "show deprecated vers…

> ~/.config/uv/uv.toml > exclude-newer = "7 days"

Note the if you get

   failed to parse year in date "7 days": failed to parse "7 da" as year (a four digit integer): invalid digit, expected 0-9 but got
then comment out the exclude and run

  uv self update

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#333
post #276

Earlier quoted context omitted.

How do you autofill from your db then?

I don't autofill. It may be less user friendly but it is not that big of a deal.

I don't save browser cookies for obvious privacy reasons and it's absolutely a big deal to not need to pull up some program and copy paste my login details constantly for every site.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#334

Earlier quoted context omitted.

The problem is that the UX with a browser extension is so much better.

Also, you want to avoid exposing your passwords through the clipboard as much as possible.

On unix-like OSes you can use `xsel` and configure it to clear clipboard after a single paste and/or after a set period of time.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#335

Earlier quoted context omitted.

I don't understand how this solves the issue in this case. Bitwarden vaults were not compromised, there was a problem in a tool you used to access the secrets. What makes it impossible for KeePass access tools to have these issues?

> I don't understand how this solves the issue in this case. I'd say since it is a local only tool, you don't really need to update it constantly provided you are a sane person that don't use a browser extension. It makes it easier to audit and yourself less at risk of having your tool compromised. It doesn't have to be keypass though, it can be any local password management tool like pass[1] or its guis or simply a…

Why are browser extensions not sane in your opinion?

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#337
post #319

Earlier quoted context omitted.

I'm guessing you meant to respond to the sibling comment rather than mine

Yes, weirdly enough at the time there was no reply button, I thought HN comments had a maximum nested depth, but now it has a reply button and so does yours. Weird.

Ah, no worries! Replies seem to get throttled sometimes when the site detects a lot of nested replies quickly and it intentionally delays the ability to reply a bit. I've always assumed that it's intended as a way to try to mitigate threads that potentially are devolving into flamewars.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#338

Earlier quoted context omitted.

But it goes the other way too. If there's a security vulnerability that was fixed in a later version, you want the system to automatically pick that up and apply it for you in an ideal scenario.

Why would you patch a security vuln in a later version? Should be patched in all versions.. that's what semver is for.

Who is 'you' here? All of the npm package maintainers?

Yes, if they all just backport security patches we'll be fine. No, people are not going to just.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#339
post #282

Earlier quoted context omitted.

That's because you're mixing things. "Rust the language" isn't the one starting new projects and add new dependencies that have hundreds of dependencies of their own, this is the doing of developers. The developers who built Rust with a focus on safety and security is not the same developers mentioned before.

Rust and Cargo are, if not inseparable, at least tightly connected. Rust and Rust's stdlib are inseparable. Cargo is modeled after NPM. It works more or less identically, and makes adding thousands of transient dependencies effortless, just like NPM. Rust's stdlib is pretty anemic. It's significantly smaller than node's. These are decisions made by the bodies governing Rust. It has predictable results.

ohh noo, the devs gave users a choice instead of forcing their hand..

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#340
> THE MOST TRUSTED PASSWORD MANAGER

> Defend against hackers and data breaches

> Fix at-risk passwords and stay safe online with Bitwarden, the best password manager for securely managing and sharing sensitive information.

yep. literally from their website this moment..and the link to their "statement"[0] is nowhere on the front page.

Oh wait, there is a top banner..."Take insights to action: Bitwarden Access Intelligence now available Learn more >" nope.

[0]: https://community.bitwarden.com/t/bitwarden-statement-on-che...

Post reply on HN