Phishing
Phishing is a social engineering attack that impersonates a trusted person or service to trick someone into revealing sensitive information, installing malware, or authorizing a harmful action.
Zelf Core Team
What Is Phishing?
A convincing message can be dangerous even when it contains no technical exploit. Phishing relies on persuasion: a supposed security alert, unpaid invoice, giveaway, or urgent request encourages you to act before checking the source.
An attacker may copy a familiar brand’s logo and website, use a lookalike domain, or compromise a real account. The request can arrive through email, text messages, social media, or other communication channels.
For example, a fake wallet-support message may claim that your assets will be frozen unless you enter your recovery phrase. The form sends that phrase to the attacker. Legitimate support does not need your wallet’s seed phrase.
How Does Phishing Work?
First, the attacker creates a believable reason to interact. A link, QR code, attachment, or reply directs the victim toward the next step.
Next, the victim encounters a request: sign in, provide a one-time code, install a program, or sign a wallet message. Some phishing systems relay a real login in real time, allowing the attacker to capture an authenticated session.
Finally, the attacker uses the information or permission obtained. A stolen password may enable account access; a malicious approval may allow token transfers. A wallet can be compromised through deception without its encryption being broken.
Why Does Phishing Matter?
Phishing targets the decisions people make around security controls. A strong password does little if it is entered on an attacker’s page, and an authentication code can be relayed while it remains valid.
Open sensitive services through a known address or trusted application. Check the actual domain and action requested, rather than relying on branding or urgency. Use phishing-resistant authentication where supported, and never send recovery phrases to support agents.
If you have disclosed credentials, use a trusted device to secure the account and revoke active sessions. If you have signed a wallet permission, review that permission specifically; changing a website password will not revoke an on-chain approval.
How This Relates to Zelf
For Zelf Secur users, distinguish protection of stored credentials from the safety of the website receiving them. For Zelf Secur and Zelf Legacy users, verify wallet requests and recovery communications carefully. Human verification can establish who is participating, but it cannot by itself establish that the destination or requested action is legitimate.