Phishing-as-a-Service Kit Scams
Ready-made criminal toolkits sold to low-skilled fraudsters enable highly convincing phishing campaigns at scale, complete with real-time credential relay, anti-detection, and automated victim management.
Last reviewed: 1 June 2026
What this scam is
Phishing-as-a-Service (PhaaS) refers to criminal platforms and toolkits that provide everything needed to run a professional phishing campaign without technical expertise. Just as legitimate software companies offer tools as a subscription service, PhaaS operators sell or rent complete phishing infrastructure to other criminals: hosting, domain rotation, pre-built fake login pages for hundreds of popular services, SMS or email sending, and dashboards for managing harvested credentials in real time.
The industrialisation of phishing through these kits has dramatically lowered the barrier to entry. Someone with no technical background can subscribe to a PhaaS platform, select a target brand from a menu — a bank, email provider, or social network — and launch a convincing phishing campaign within minutes. The kit handles the technical elements: HTTPS certificates on the fake site to display the padlock icon, real-time credential relay to bypass two-factor authentication, and anti-bot measures to make the fake page harder for security researchers to detect.
For ordinary users, the practical effect is an increased volume of highly convincing phishing attempts. Because PhaaS kits are maintained by experienced operators who track security changes at target services, the fake login pages are often indistinguishable from genuine ones. The credential relay capability is particularly dangerous: it passes your username, password, and one-time code to the real service in real time while harvesting them, meaning even two-factor authentication can be bypassed during the live session.
How it works
A PhaaS operator creates and maintains a platform containing fake login pages for popular services, infrastructure to host them on rotating domains to avoid blocklisting, and a control panel. Criminal buyers — known as affiliates — subscribe to the platform, select the target brand, and receive a campaign link or deploy the pages on provided hosting.
The campaign link is sent to victims via phishing email or SMS. The victim clicks and arrives at a convincing fake login page. When they enter their credentials, the PhaaS platform either stores them for the affiliate to use later or — in adversary-in-the-middle kits — relays them to the genuine service in real time, logs the victim in, captures the session token that results, and gives the affiliate live authenticated access.
The real-time relay capability means that even if the victim uses an authenticator app, the attacker captures the session after the code is entered — the attack succeeds because it hijacks the resulting authenticated session rather than the credentials themselves.
The affiliate dashboard shows harvested credentials, session tokens, and campaign statistics. Advanced kits include victim-geofencing (only show the fake page to targets in a specific country), Cloudflare bypass techniques, and automatic SMS delivery through carrier APIs.
Why this scam works
PhaaS kits succeed because they combine technical sophistication with low cost of entry. The fake pages they produce are maintained to accurately mirror current genuine sites — including security indicators like the HTTPS padlock — removing visual cues that previously helped users identify fakes.
The subscription model means that the criminals running actual phishing campaigns are often not technically skilled and cannot be deterred by raising technical barriers. Even when security researchers discover and block individual fake domains, the kit operator rotates to new ones automatically.
For victims, the adversary-in-the-middle variant offers no easy defence beyond hardware security keys — even vigilant, two-factor-enabled users can be compromised if they enter credentials on the fake page and the kit relays them in real time.
A typical pattern
A person receives an SMS that appears to be from their bank, warning that their account access has been temporarily restricted. The link in the message leads to a page that is visually identical to their bank's login, including the HTTPS padlock. They enter their username and password, then receive an SMS code from their real bank — because the PhaaS kit relayed their login to the genuine site in the background. They enter the code on the fake page. The kit captures the resulting authenticated session. The attacker uses the session to access the account before the person notices anything unusual.
Common red flags
- URL in the browser bar is not exactly the service's official domain
- Login page link arrived via SMS or email rather than direct navigation
- Page appeared after clicking a message about account restriction, security alerts, or unusual activity
- You are asked to enter a one-time code on a page you reached by clicking a link
- The page loaded unusually quickly or the branding is very slightly off
- You receive an unexpected SMS verification code you did not request
Sanitized example messages
Illustrative, sanitized examples. Personal details are replaced with placeholders such as [phone number] and [fake link].
Your [bank] account has been restricted. Log in to restore access: [fake link]
[Email provider] security alert: unusual sign-in detected. Verify your account: [fake link]
[Service]: Your password needs to be reset to maintain security. Click here: [fake link]
Important: your [crypto exchange] account will be suspended unless you verify your identity today: [fake link]
Common variations
- Adversary-in-the-middle (AiTM) variant — real-time credential relay to bypass two-factor authentication
- Reverse-proxy variant — entire genuine site proxied in real time to avoid visual detection
- Telegram-bot delivery — harvested credentials automatically sent to attacker via messaging app bot
- Bulk SMS variant — PhaaS combined with carrier API access to send high-volume smishing campaigns
How to verify before you act
Check the URL in your browser's address bar before entering any credentials. PhaaS kits rotate through convincing-looking domains, but the URL will not be the service's exact official domain. A slight variation — an extra hyphen, a different TLD, a subdomain on an unrelated domain — is a strong indicator of a fake page.
For your most important accounts, use a hardware security key for two-factor authentication. Hardware keys are bound to the genuine domain and will refuse to authenticate on a fake page, even one that is visually identical.
Be especially sceptical of login page links received via SMS or email, even when they appear to come from the genuine sender. Navigate to services directly by typing the address yourself or using a bookmark rather than clicking links in messages.
Payment methods used
- Direct banking session takeover
- Cryptocurrency account access via stolen session token
- Stored card charges via compromised e-commerce accounts
Who is usually targeted
- Banking customers receiving security or restriction notices
- Email service users receiving account-verification requests
- Cryptocurrency exchange users receiving login alerts
- Anyone who clicks links in SMS or email messages to log in
What to do immediately
- Do not enter credentials on any page reached via a link in an unexpected message
- If you already entered credentials, change your password on the genuine service immediately
- If you entered a one-time code, contact the service to report a potential session compromise
- Enable a hardware security key on high-value accounts if supported
- Report the phishing link to the genuine service's security team and to national fraud authorities
How to prevent it
- Use hardware security keys (FIDO2/WebAuthn) for two-factor authentication on banking and high-value accounts — these are domain-bound and defeat AiTM attacks
- Never click links in unexpected messages to log in — navigate directly to services by typing the address
- Check the full URL before entering any credentials, even on pages that look genuine
- Enable login alerts so new session activity triggers an immediate notification
- Use a password manager that auto-fills only on the exact registered domain, providing a passive check against fake pages
Evidence to preserve
- The URL of the fake page
- Screenshot of the phishing message and any fake login page
- The sender's phone number or email address
- Timestamps of when credentials were entered and when the compromise was noticed
Where to report it
- Action Fraud (UK) — UK national fraud & cybercrime reporting centre
- FTC ReportFraud (US) — US Federal Trade Commission fraud reports
- FBI IC3 (US) — US Internet Crime Complaint Center
- Scamwatch (Australia) — Australian competition & consumer reporting
- Your bank's fraud line — Use the number on the back of your card or in your banking app — never a number the caller gives you
Always verify reporting routes and emergency contacts on the official government or agency website for your country.
Frequently asked questions
If the page has a padlock, does that mean it is safe?
No. HTTPS and the padlock icon mean only that the connection between your browser and the server is encrypted. It says nothing about whether the server is operated by the genuine company. PhaaS kits obtain HTTPS certificates trivially. Always check the full URL, not just the padlock.
Can two-factor authentication stop PhaaS attacks?
App-based two-factor authentication can be bypassed by adversary-in-the-middle kits that relay your code in real time. Hardware security keys bound to the genuine domain cannot be bypassed this way — they refuse to authenticate on a fake page regardless of how convincing it looks.
How do attackers get PhaaS kits?
PhaaS platforms are sold and rented on criminal forums and through encrypted messaging channels. They are commercially operated with customer support, feature updates, and subscription pricing — essentially a shadow software-as-a-service industry.
How quickly does an attacker act after credentials are captured?
In AiTM variants, the session is compromised in real time — within seconds of the victim logging in. The attacker may act immediately, or the session may be sold to another criminal. Speed of detection matters enormously: changing passwords and contacting the service within minutes can limit damage.