Phishing
What is phishing?
Phishing is a social-engineering cyberattack that uses deceptive messages, websites, or requests to trick people into revealing credentials, approving access, or installing malicious software. It can target email accounts, cloud services, developer tools, API keys, session tokens, and application users. Unlike a software vulnerability, phishing manipulates a person into taking an unsafe action.
How a phishing attack works
Attackers make a request appear routine, urgent, or trustworthy.
- They research a company, product, or person to make the message believable.
- They impersonate a brand, colleague, identity provider, or support team.
- They send a link, attachment, QR code, chat message, SMS, or fake login page.
- The recipient signs in, enters a code, approves an app, or opens malicious content.
- The attacker captures credentials or tokens and uses the account.
Opening an email usually does not cause phishing. Risk begins when someone clicks, signs in, downloads, or approves access. Rarely, malicious content exploits an unpatched software flaw, so updates still matter.
Common types of phishing attacks
These common forms differ mainly by channel and target.
| Type | Typical channel | Requested action |
|---|---|---|
| Bulk email phishing | Click a fake sign-in link | |
| Spear phishing | Email or chat | Respond to a tailored request |
| Business email compromise | Change payment or account details | |
| Smishing or vishing | SMS or phone | Share a code or visit a link |
| QR-code phishing | QR code | Open a fraudulent login page |
| Consent phishing | OAuth prompt | Grant a malicious app permissions |
How to recognize a phishing attempt
The strongest red flag is often an unexpected request to act, not poor grammar.
- Lookalike sender domains or links that do not match the claimed service.
- Unexpected password, one-time-code, or authentication requests.
- Pressure to bypass approvals or act immediately.
- Unusual attachments or unfamiliar cloud-file sharing notices.
- OAuth prompts asking for more access than an app needs.
What to do if you clicked or shared information
Fast reporting helps security teams revoke access before account takeover spreads.
- Stop interacting with the message. Disconnect the device only if malware is suspected.
- Report it through the organization’s security process.
- From a known-safe device, change the password and revoke active sessions.
- Remove suspicious app permissions and rotate exposed API keys or secrets.
- Ask the identity or security team to review sign-in and audit logs.
Phishing prevention for apps and development teams
Effective defenses reduce deception and the damage from one mistake.
- Use passkeys or hardware security keys where possible, plus multifactor authentication.
- Store secrets in managed systems, never in source code or chat messages.
- Apply least-privilege roles, review OAuth consent, and retain audit logs.
- Design clear sign-in screens and safe reporting paths.
- Use shared definitions from the Emergent glossary when documenting security requirements.
Why phishing matters when building software with Emergent
When building web or mobile products with an AI app builder, phishing prevention should shape sign-in flows, permissions, secret handling, testing, and deployment checks. Teams can apply secure design practices during app design and development so a convincing message cannot easily become unauthorized access.
on Emergent today

