Thank you for bringing this to our attention. This appears to be a legitimate update and the updated DropboxUpdateClient binary should be signed with the Dropbox signature. However, there seems to be an issue with how the identifier is being set for this binary. We will investigate this issue further to ensure the identifier is set consistently.

gpswuser

Hi Suyeon,

Thank you for replying! I look forward to hearing back about the identifier for the updated DropboxUpdateClient, and if this new identifier is valid.

Nancy

Hey @gpswuser! Hope you’re doing well and thanks for your patience.

The issue should now be fixed in the latest app version (205.4.5765) that was released yesterday.

Can you make sure your Dropbox app is running that version and let us know if the issue persists?

gpswuser

Hello!

I have confirmed I am running version 205.4.5765, but Little Snitch now shows this:

Screenshot 2024-08-08 at 10.27.23 AM.png

Is the correct/valid identifier now "DropboxUpdateClient"?

Thanks,

Greg

mhutchens

Hi @gpswuser,

Sorry for the late reply!

Yes "DropboxUpdateClient" is the correct identifier and it should not change anymore. Thank you again for bringing this to our attention!

gpswuser

Hi @mhutchens,

Thank you for your reply - much appreciated!