1 files changed, 24 insertions, 0 deletions
diff --git a/packages/meshbay-hub/src/meshbay_hub/api/users.py b/packages/meshbay-hub/src/meshbay_hub/api/users.py
index a994acb..7046c2f 100644
--- a/packages/meshbay-hub/src/meshbay_hub/api/users.py
+++ b/packages/meshbay-hub/src/meshbay_hub/api/users.py
@@ -728,6 +728,14 @@ async def get_current_user_info(
 
 class UpdateProfileRequest(BaseModel):
     email: str | None = None
+    # Required to change the address on file. Changing it is the first step of
+    # an account takeover from a bare access token: the confirmation code goes
+    # to the new (attacker) address, and a verified address then unlocks the
+    # passphrase-reset path. A live access token is not enough for that — the
+    # passphrase is, exactly as for `change_password` and `delete_own_account`.
+    # This matters because a member hands its access token to every node it
+    # connects to (the MNP handshake), so a node operator holds one.
+    auth_key: str | None = None
 
     @field_validator("email")
     @classmethod
@@ -768,6 +776,22 @@ async def update_profile(
         new_email = body.email.strip()
         eh = hash_email_blind(new_email)
 
+        # Changing the address on file requires the passphrase, not merely a
+        # live token. Same second factor, and the same throttle, as a passphrase
+        # change or an account deletion — the hub still never sees the
+        # passphrase, only the derived auth_key.
+        if not body.auth_key:
+            raise HTTPException(
+                status_code=403,
+                detail="Changing your e-mail requires your passphrase.")
+        await _take_login_attempt(db, current_user.username)
+        if not await verify_password_off_loop(
+                body.auth_key, current_user.pw_hash, current_user.pw_salt,
+                current_user.pw_version):
+            raise HTTPException(status_code=403,
+                                detail="Passphrase does not match")
+        await login_throttle.clear(db, current_user.username)
+
         # How often one account may point the hub at a *different* address.
         # Long, because this is the only path where a signed-in account chooses
         # who receives a message, and a short delay alone still allows one