Possible KDB (1.x) corruption after adding an entry via AutoFill

[keepassium]

Description

KDB files (KeePass 1.x format) do not support entries in the root group, they must be placed in a subgroup. However, AutoFill creates new entries in the root group by default — which makes the database unreadable in KeePassium itself, while KeePass 1.x does not "see" the added entry.

This does not apply to KDBX (KeePass 2.x) databases, nor when new entries are created by AutoFill in non-root group.

How to reproduce Steps to reproduce the behavior:

• Open some web login form, then open AutoFill interface
• Select a .kdb database
• Tap "Create Entry", keep the default entry location
• Save changes
• Try opening the database
• Observe error: "Found an entry outside any group. Corrupted DB file?"

Environment:

• Device: any
• OS: any
• App Version: 2.4

[keepassium]

Workarounds

1. Quick, but destructive

• Open the affected database with KeePass 1.x.
• Save the file
• This will delete the entry added by AutoFill, and database will load normally again.

2. Slower, but future-proof and preserves all data

• Install KeePassXC and convert your database to KDBX (KeePass 2.x) format:
  • Open menu Database → Import → KeePass 1 Database…
  • Select your .kdb database and unlock it with your master password/key file
  • KeePassXC will load your data — including the latest entry — and offer to save it as a .kdbx file

This is the best approach. The extensible KDBX format was introduced in 2008, but for a while was not supported by other apps, so KDB was a safer choice. However, that was 17 years ago and now KDB is on life support. The old format is just not tested that thoroughly anymore, which was the main cause of this bug. We will surely fix the bug, but would strongly recommend everyone to upgrade to KDBX format.