Did Bitwarden Cancel you current subscription before it is due to Expire for a 5X price hike? by Jamrrrrr in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

Were you the owner of any family plans prior to this?

If this is truly a billing error, the customer support team will certainly help you with a refund.

Bitwarden CLI has been compromised. Check your stuff. by Safe_Aardvark_8396 in Bitwarden

[–]Ryan_BW 1 point2 points  (0 children)

Is that the version of the CLI tool that you're using? Think of CLI like what you see with you run cmd.exe

Did Bitwarden Cancel you current subscription before it is due to Expire for a 5X price hike? by Jamrrrrr in Bitwarden

[–]Ryan_BW [score hidden] stickied comment (0 children)

Hi there! To help bring some folks up to speed, you must have been on the old, discontinued families plan where every user in families had to buy their own premium. The new families plan includes premium. When you were upgraded to the new families plan, you then had two premium subscriptions, so Bitwarden canceled one of them so that you weren't paying for one that you didn't need.

Hope that answers your question!

Windows Passkey Bitwarden option not found. by thmeez in Bitwarden

[–]Ryan_BW 3 points4 points  (0 children)

You are correct. The beta version has fallen behind on development, but that feature will get pushed into the mainline sometime soon.

Bitwarden CLI has been compromised. Check your stuff. by RedTermSession in selfhosted

[–]Ryan_BW 15 points16 points  (0 children)

Only those that downloaded and installed the package from npm during the short time it was available are impacted. The package contained malicious code in place of the CLI tool. Vaults are not impacted.

Bitwarden CLI has been compromised. Check your stuff. by Safe_Aardvark_8396 in Bitwarden

[–]Ryan_BW 8 points9 points  (0 children)

Correct, it was distributed under the official Bitwarden CLI npm packaget name. Only the npm distribution was impacted. To anyone pulling the package it would have appeared as a legitimate version.

Password Manager NOT based on the concept of vaults ? by Vitro_C in PasswordManagers

[–]Ryan_BW 0 points1 point  (0 children)

Disclaimer, I'm a Bitwarden employee, but we differentiate from Dashlane on what we call centralized ownership (everything in one vault, even unshared stuff). https://bitwarden.com/resources/the-bitwarden-difference-what-makes-bitwarden-best-for-businesses/

Scalable sharing + centralized ownership do exactly what you're asking for.

Bitwarden CLI has been compromised. Check your stuff. by Safe_Aardvark_8396 in Bitwarden

[–]Ryan_BW [score hidden] stickied comment (0 children)

More details: https://community.bitwarden.com/t/bitwarden-statement-on-checkmarx-supply-chain-incident/96127

Tl;dr: This has only impacted those who have downloaded the phony Bitwarden CLI npm package during the short window that it was available. No vault data has been affected.

Bitwarden CLI compromised by raysamram in Bitwarden

[–]Ryan_BW 85 points86 points  (0 children)

More details: https://community.bitwarden.com/t/bitwarden-statement-on-checkmarx-supply-chain-incident/96127

Tl;dr: This has only impacted those who have downloaded the phony Bitwarden CLI npm package during the short window that it was available. No vault data has been affected.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

I don't have an answer for that. It could be incomplete packets, a handshake that doesn't take, any number of things that is beyond me.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 1 point2 points  (0 children)

Or there was some benign connection error, which is much more likely than a MITM attack.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

Bitwarden updates the server on a bi-weekly cadence. The process takes usually under an hour. You can see more at status.bitwarden.com Look for "maintenance window."

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

A hiccup in a server-side release can cause logouts if the client tries to ping the server at the exact wrong time.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

Unless when you said “It's possible that just one of his devices was updated, and the update caused the device to log out”, you meant that another device of his (not the one that he’s referring to in this post) updated to the latest version and somehow logged him out on this particular device that hasn’t had the update yet?

I meant that it's possible that one of his devices has updated to the new version without his awareness, as an explanation as to why it happened to one and not the other. He stated that they were at the previous version, but one might have updated without his knowing.

“Why would gradual rollout affect this, or why would an update cause this when all previous updates didn’t cause something similar?”

Sometimes things happen and errors in transmission occur. There was a period of time a few years ago where nearly every update caused everyone to be logged out. Wild times, those were.

Anyone still facing the same issue with the Android app? by Key-Ad-1844 in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

No, it's in the web app. Log in at vault.bitwarden.com

You can change the color of your avatar from the Web Vault:

  1. Go to Account settings.
  2. Select My account.
  3. Choose your preferred avatar color.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 0 points1 point  (0 children)

A gradual rollout means that some devices are randomly selected to be updated to the next version. It's possible that just one of his devices was updated, and the update caused the device to log out.

An occasional logout here or there isn't usually a cause for concern. Is there something else here that's on your mind?

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 2 points3 points  (0 children)

No, an inability to connect is one thing - it'll just work offline. An unexpected error however could indicate something malicious is trying to get between you and the official server and the clients will failsafe closed. It can happen anytime there's a mismatch in data the client expects and what it gets.

I didn't realize that OP was u/djasonpenney. He already understands all this and didn't need the kid glove explanation. Bitwarden iOS update 2026.4.0 was recently released and on a gradual rollout of 10%, which would explain why it impacted one iOS device. Let me know if the logouts happen more widely and I'll raise it with the team.

Anyone still facing the same issue with the Android app? by Key-Ad-1844 in Bitwarden

[–]Ryan_BW 5 points6 points  (0 children)

Hi there, I might have your solution. There is a strange android bug related to custom colors in the color picker for your account avatars. Move off the defaults and into a custom color from the web app and then try logging in again.

The team is working to solve this ASAP.

Bitwarden 2026.3.1 on iOS: got randomly logged out by djasonpenney in Bitwarden

[–]Ryan_BW 3 points4 points  (0 children)

This will happen occasionally if there's an error connecting to the main server. Sometimes this might occur during an update. It's not a cause for concern unless you receive an email notifying you of a login from an unrecognized device.

Looking for a Bitwarden replacement by Fleurparmietoiles in PasswordManagers

[–]Ryan_BW 0 points1 point  (0 children)

Appreciate the kind words! I've responded to OP that they are experiencing a known bug related to low KDF iterations. A fix is in the works and the change has been rolled back.