2FAuth exposure begins with account ownership and personal access tokens
2FAuth stores and generates one-time authentication codes for other services. That makes the application a compact credential vault with a user-facing API. A reachable instance is not automatically compromised, but its account model, API tokens, and sharing features deserve a careful review before it is treated as an internal convenience.
The official 2FAuth API uses personal access tokens with OAuth bearer authentication. Tokens are created in the user's settings, and the documentation says revoked tokens can no longer authenticate to the API. The administration guide also states that authorized users can generate valid codes, which is the operational consequence of access to the stored accounts. A token with that authority should be handled as a credential, not as a read-only integration key.
Version 7 added sharing of 2FA accounts between users. The documentation states that sharing keeps management capabilities consistent with ownership and that ownership can be transferred in a controlled way. This is a useful feature, but it means a user inventory alone does not describe who can generate a code for a given account. Review owners, shares, transfers, and revocation paths together.
Query plan
The reproducible baseline is app="2FAuth" and the separate title candidate title="2FAuth", both with sub_type=all, page 1, and page size 1. The application field tests the product fingerprint; the title field tests a visible page marker. They are not the same population. A live count was not available in this run because the authorized ZoomEye execution path was rejected by the execution platform, so no observation is asserted here.
Use the two counts as a discovery clue. They should not be summed. If one query succeeds and the other fails, record the failure rather than treating it as zero. If both produce counts, compare the collection time, query scope, and page size before drawing a conclusion.
Review the authority path
Start with the administrators and the users who can create personal access tokens. Confirm that registration is controlled, that dormant users are removed, and that password reset and SSO paths match the intended access model. Review the application encryption key and its rotation procedure. Changing the key can affect sessions, encrypted data, WebAuthn, and tokens according to the environment documentation.
Inventory API clients by token owner. A token's label is not proof of its scope. Test whether a revoked token fails immediately, whether a disabled user retains a valid token, and whether a shared account remains usable after its owner changes. Review the audit trail for token creation, deletion, and account sharing.
Check the storage of icons, backups, and application logs. TOTP secrets and recovery material should not appear in diagnostic exports. Capture support bundles in a controlled location, and restrict who can read the database and encryption-key configuration.
Network and response
Expose the 2FAuth web interface only to the users and networks that need it. Put administrative access behind a trusted proxy or VPN if the organization's access model permits it. Do not rely on an obscure URL. If the instance is public, require strong authentication, monitor failed logins, and test account recovery from an untrusted client.
For an unexpected match, verify the page content and response instead of contacting the host. Check the product version through an authorized administrative path, review recent account changes, and revoke tokens that cannot be tied to an owner. If the instance is unauthorized, isolate it and preserve the evidence before deleting data.
2FAuth is small enough to be overlooked in an asset inventory. Its data is sensitive enough to justify the same ownership and token review applied to a password manager. The query identifies candidates; the account model determines whether a candidate matters.

