Password Pusher separates secret links from management authority
Password Pusher creates expiring links for passwords, text, files and URLs. ZoomEye returned zero matches for app="Password Pusher" and 537 for title="Password Pusher" on 2026-11-22, using sub_type=all, page 1 and page size 1.
The zero application result is a discovery limitation. The title result is the usable lead, although it can include documentation and hosted-service pages.
The matches are not confirmed deployments or exposed pushes.
Two different access paths
The recipient uses a push link. The link may expire, allow a limited number of views, or require a passphrase. That path is intentionally available to someone outside the organization.
The administrator path is different. The official administration documentation describes /admin, a system-admin role and options such as two-factor authentication. The API v2 documentation describes bearer-token authentication for creating, retrieving and managing pushes.
An exposed application does not mean an exposed admin account. Review the routes separately. A public push should not provide management rights, and an API token should not be pasted into a push.
Inventory
Look for owned Password Pusher deployments by title, certificate and service owner. Record the public base URL, version, authentication mode and whether the admin dashboard is reachable.
Inspect the reverse proxy rules that expose /admin, the API and public push routes. If the service is meant for a small team, restrict administration to SSO or a management network.
Review API token scope and lifetime. Remove tokens that belong to former staff or abandoned integrations. Check whether a token can manage other users or only create a push.
Secret lifecycle
Set expiration and view limits that reflect the sensitivity of the content. A short-lived link is easier to contain than one that remains valid until someone remembers to revoke it.
Passphrases help when the link travels through a channel that may retain it. Send the link and the passphrase through different channels where possible.
Do not put secret values in application logs, analytics, browser page titles or notification previews. Review inbound email and chat scanners that may open links automatically. A scanner can consume a one-time link before the recipient does.
Monitoring
Alert on new administrator accounts, token creation, changes to authentication settings, repeated failed passphrase attempts and a sudden rise in push creation.
Correlate an admin login with reverse-proxy and application logs. Keep enough metadata to identify the source and route without recording the secret.
Measurement limits
The 537 title matches provide a broad candidate set. The absence of an app fingerprint means the title and page structure need manual review.
State that limitation in any report. The useful question is not how many pages mention Password Pusher. It is which owned services separate public push access from administrative and API authority.