[GH-ISSUE #2486] [FEATURE] Decoy Vault #1277

New issue

Closed

opened 2026-03-03 02:07:46 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:07:46 +03:00

Owner

Originally created by @knightian on GitHub (May 24, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2486

I had a thought about a useful feature.

What if Vaultwarden could detect a wrong password and use it to supply a decoy vault? So you have an account (email) that has it's normal master password, but you have also another master password attached to the same account (email) that if you supply under coercion it unlocks a decoy vault full of decoy password values.

Originally created by @knightian on GitHub (May 24, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2486 I had a thought about a useful feature. What if Vaultwarden could detect a wrong password and use it to supply a decoy vault? So you have an account (email) that has it's normal master password, but you have also another master password attached to the same account (email) that if you supply under coercion it unlocks a decoy vault full of decoy password values.

kerem closed this issue

2026-03-03 02:07:46 +03:00

kerem commented

2026-03-03 02:07:46 +03:00

Author

Owner

@BlackDex commented on GitHub (May 24, 2022):

Sounds like a truecrypt feature.
But that isn't something which can be done by this project it self. Since the clients need to support that too.

Also, if you were coerced, they would probably check the results first and keep trying to get it out of you.

@BlackDex commented on GitHub (May 24, 2022): Sounds like a truecrypt feature. But that isn't something which can be done by this project it self. Since the clients need to support that too. Also, if you were coerced, they would probably check the results first and keep trying to get it out of you.