mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #2420] Bot spammed database what should i do? - Admin Panel can't load anymore. Over 40K Accounts have been created... #1255
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1255
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Skyfay on GitHub (Apr 15, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2420
A bot has spammed my Vaultwarden with an extremely large number of accounts.
He has apparently created over 40,000 accounts.
Fortunately, the performance is good, but the Admin Panel tab users now loads extremely slowly.
Is there a command to remove these users at once with one command?

Is there a possibility that users who have created an account but have not logged in for 1 week will have their account deleted?
If these accounts were created with the same IP, I think that's a security risk...
What should I do now?
@BlackDex commented on GitHub (Apr 15, 2022):
You could try to solve this in two ways.
Either use the admin API via curl or something. there is a
/admin/usersendpoint which returns all the users with all the info as a json. You could use that to filter those users. And then generate aPOSTto/admin/users/<uuid>/deleteto delete these users.That would be the safe way.
The other way would be to delete these users directly from the database.
It should just be as easy as removing those users from the
userstable.You may also need to remove the from the
invitationstable, but I'm not sure from the top of my head.Both options should work. And looking at the users since they are not linked to an organizations or have any vault items, both should work just fine.