ensure the at-risk-passwords page navigates back to the vault

apps/browser/src/vault/popup/components/at-risk-passwords/at-risk-passwords.component.html

@@ -1,5 +1,10 @@
 <popup-page [loading]="loading$ | async">
-  <popup-header slot="header" [pageTitle]="'atRiskPasswords' | i18n" showBackButton>
+  <popup-header
+    slot="header"
+    [pageTitle]="'atRiskPasswords' | i18n"
+    showBackButton
+    [backAction]="navigateToVault.bind(this)"
+  >
     <ng-container slot="end">
       <app-pop-out></app-pop-out>
     </ng-container>

apps/browser/src/vault/popup/components/at-risk-passwords/at-risk-passwords.component.ts

@@ -223,4 +223,13 @@ export class AtRiskPasswordsComponent implements OnInit {
       this.launchingCipher.set(null);
     }
   };
+
+  /**
+   * This page can be the first page the user sees when the extension launches,
+   * which can conflict with the `PopupRouterCacheService`. This replaces the
+   * built-in back button behavior so the user always navigates to the vault.
+   */
+  protected async navigateToVault() {
+    await this.router.navigate(["/tabs/vault"]);
+  }
 }