Business Funding Phishing: The Form That Wants Your Revenue, Not Your Password

Cover graphic on a deep navy field. The headline reads They do not want your password. To the right, a dark form panel lists five filled fields, gross revenue, amount wanted, credit score, role and tenure, above a red submit bar, tagged a profile you cannot revoke.

Bottom line up front

A long-running phishing operation is impersonating Small Business Administration lending programs, and it is not trying to steal a password. It wants a form filled in: your gross revenue, how much you want to borrow, your personal credit score, your role and how long you have been there. That is a profile rather than a credential, which means you cannot revoke it, and it is exactly what makes the follow-up phone call sound like it already knows you. Microsoft measured up to 2.37 million of these messages in a single weekday. Your filter probably caught the email — but the same pitch also arrives by phone, and there is no filter on the phone.

The email is addressed to your company by name. It says rates have dropped, that you may qualify, and that there is a window. If you have spent any time this year trying to get a line of credit, none of that reads as an attack. It reads like the thing you have been waiting for.

That is the entire design. And the part worth understanding is not how the email got into your inbox. It is what the page at the end of it asks you for, and why that turns out to be worth more to the sender than your password would have been.

Six tells in a funding offer

If one just landed and you want the short version, check these six. None of them depend on recognizing a technique, which matters because the techniques get replaced and these do not.

  1. You did not apply. The SBA’s Office of Inspector General is direct: SBA communicates only from addresses ending @sba.gov, and anyone claiming to be SBA from anything else should be treated as fraud. Lenders answer applications. They do not open conversations.
  2. The sender domain is a word salad. guardiangrowthfunding, digitalcapitalboost, advancefundingboost. Microsoft’s sample of 148 campaign domains was built from a vocabulary of 28 words, recombined and rotated. Read it out loud; if it sounds assembled rather than named, it was.
  3. The amount arrives before the application does. A number and a timeline, with no knowledge of your books. The FTC’s rule: nobody legitimate promises a loan without knowing your credit history.
  4. The first ask is information, not money. Revenue, amount wanted, credit score, role, tenure. That is not an application. It is a profile.
  5. There is a logo doing work a logo cannot do. SBA OIG says it plainly: an SBA logo on a page does not mean SBA endorsed anything on it.
  6. The exit is a phone number. Submit the form and the page thanks you, then suggests calling for a faster response. That is not service. It is the handoff to the part of the operation that works on people.

Definition

Business funding phishing is a lure built around a loan, line-of-credit or advance-funding offer, usually wearing the branding of a real lending program. Unlike a credential phish it often takes no password at all — the payload is a questionnaire that harvests financial and personal detail to make a later, better-targeted approach succeed.

What the form actually asks for

The security vendor Fortra documented this operation in detail. Its September 2025 analysis is a year old now, and it remains the clearest account of what happens after the click — Microsoft’s 2026 research connects the campaign it was still tracking back to exactly this one.

The lure impersonates the SBA’s line-of-credit programs. Subject lines run off a handful of templates with the company name dropped in: Good News, <Company> — SBA Rates are Down!, Limited Window: Lower SBA Rates for <Company>. One batch leaked part of its own automation, exposing the %company% parameter being filled per recipient.

Click, and the page was generated for the occasion. Fortra found them AI-produced: one template, different branding, layout and stock faces each time, hosted on reputable infrastructure so the domain reputation looks ordinary. Almost nothing on the page works. Navigation is inert, and every button leads back to the single live element, which is a questionnaire asking for:

Then a pop-up thanks you, says someone will be in touch, and offers a number to call for a faster response.

Figure 01 · Four steps, and the last one is the product
1REGISTERDisposable finance-themed domainsMicrosoft’s sample of 148 sender domains was built from avocabulary of 28 words, recombined and rotated.2RELAYSend through a real marketing platformSPF, DKIM and DMARC all pass. Nothing is spoofed. Every link isrewritten to the platform’s own tracking domain.3LANDAn AI-generated page, varied per recipientNavigation is inert. Every button leads back to the one element thatworks, which is a questionnaire.4HARVESTTHE POINTRevenue. Amount wanted. Credit score. Role. Tenure.Not a password — a profile. It stays true for months, and it is whatmakes the follow-up call sound informed.

Sender-domain and relay detail per Microsoft Security Research, 3 September 2026. Landing page and questionnaire fields per Fortra Intelligence and Research Experts, 18 September 2025, documenting the earlier phase of the same campaign.

Why a profile is worse than a password

Fortra’s assessment of the objective is the sentence to put in front of anyone who thinks their filter settled this: the operation is not after an immediate credential or payment. It is harvesting detailed business and financial information to enable highly targeted spear-phishing later.

You cannot rotate a profile

A stolen password is revoked on Tuesday afternoon and the problem is over. A record saying your company bills roughly this much, wants roughly this much, is run by a person with this job title and this much tenure, and is actively looking for money right now cannot be revoked. It stays accurate for months. And it is precisely what is needed to write the convincing follow-up: the broker who knows your number, the underwriter calling about the application you really did fill in.

We have written that follow-up from the other end. A vendor-impersonation email that already knows your payment terms is not guesswork. This campaign is the reading somebody did first.

Why it arrived looking legitimate

Nothing in this campaign is spoofed, which tends to surprise people who have spent money on email authentication.

The mail was relayed through infrastructure associated with ActiveCampaign, a real and widely used email-marketing platform. So SPF, DKIM and DMARC pass, because the platform genuinely is sending on behalf of a domain the operator genuinely controls. IP reputation reads as marketing traffic. And every link is rewritten to the platform’s own click-tracking domains, so the URL your user hovers over does not point at the strange finance domain at all.

Microsoft shared its findings with ActiveCampaign before publishing. The company says it tested the technique against its content moderation, that messages containing invisible Unicode get the same verdicts as their unobfuscated equivalents, and that heavy use of it is itself treated as suspicious. That is a reasonable answer, and it does not change the structural problem Microsoft states carefully: with any shared sending service, abuse of customer accounts complicates reputation-based filtering, because the activity looks like legitimate marketing traffic.

Worth sitting with, if your defensive story is mostly authentication. DMARC tells you a message really came from where it says. It does not tell you the sender is honest — the same point as device-code phishing on Microsoft 365, where every step is a genuine Microsoft flow doing what it was designed to do.

The invisible character, and why it is a footnote

This campaign got written up in September for a detail that turns out to be the least important thing about it, and it is worth knowing because it tells you something about where your defenses actually sit.

Microsoft’s researchers found the operator wedging invisible Unicode characters into the middle of finance words. funding was sent as fun⟨U+E0020⟩ding. To you it still reads as funding. To a detector matching the literal string, the word is not there. The technique is called ASCII smuggling, and it became well known through AI prompt-injection research, where invisible characters from the deprecated Unicode Tags block (U+E0000 to U+E007F) are used to hide instructions from a human while leaving them visible to a model. Here the intent is inverted: nothing is hidden from you, only from the filter.

It did not work. Microsoft reports that over 99% of these messages were flagged anyway, by layers that never looked at those characters — sender and URL reputation, machine-learning classification, brand-impersonation detection, authentication checks. And because tag characters are almost absent from ordinary mail, using them handed defenders a low-false-positive signal. The evasion was a flare.

A technique meant to make messages look more benign ended up giving defenders a high-confidence way to find them.

The dates bound the technique, not the campaign. Microsoft’s signature went from firing on ~21,000 messages on 8 February 2026 to more than 1.3 million the next day, ran on a strict weekday-on, weekend-off schedule through a high-volume phase, and dropped off after 15 May. The operation ran before the Unicode characters appeared and carried on after they stopped. The trick came and went. The business did not — which is the argument for spending your attention on the form rather than the encoding.

A business looking for money has already lowered the drawbridge

Every phishing control your team has been trained on assumes the message is unwelcome. Nobody wants a password reset they did not request, or an invoice from a supplier they have never used. The training works partly because the email is an intrusion.

A funding offer is not an intrusion if you are looking for funding. Fortra makes exactly this point about why the SBA programs were chosen: they appeal to businesses seeking funding and the promise of financial relief, which can override normal caution — and smaller firms run with less defensive budget, which is why they get picked.

So the failure here is not really a filter failure. Most small businesses have no process for an inbound offer of good news. There is a callback rule for payment changes, probably a rule about wire requests from the owner, and almost never a rule that says we do not give financial details to a lender who contacted us first. That category does not exist, because it never looked like a threat category.

Four rules that survive any version of this

Figure 02 · None of these care how the email was encoded
1RULE 1 · THE ONE THAT DOES THE WORKYou pick the lender. It does not pick you.Financing starts with an application you filed. An unsolicited offer is alist you are on.2RULE 2 · SBA OIGGovernment mail comes from a government domainSBA writes only from @sba.gov, and an SBA logo on a page endorsesnothing. Verify on 1-800-827-5722.3RULE 3 · FTCNo fee before a loan. Ever.A lender may charge to consider you. None promises the loan andthen charges for it.4RULE 4 · THE HABIT UNDERNEATHVerify on a channel they did not chooseA number you looked up. A register they cannot edit. Never thenumber on the page that sent you.

Rules derived from SBA Office of Inspector General guidance on loan and phishing fraud, and FTC consumer guidance on advance-fee loans. Both are cited in full above.

All four are process rather than technology, which is the honest summary of this whole story. The last one — verifying through a channel the other party did not choose — is the same muscle that catches the fake help desk and the fake bank fraud department, and it is worth rehearsing precisely because it feels rude in the moment.

What the IT side should change

If you have an internal IT person or an MSP, Microsoft’s guidance reduces to one sentence that generalizes well past this campaign: normalize before you match.

ChangeWhy
Strip or fold invisible code points before content rules run The tag block U+E0000–U+E007F, plus zero-width space, zero-width non-joiner, no-break space and soft hyphens. Any keyword, regex or signature logic should see normalized text, not raw bytes. This is the actual fix.
Alert on tag-block characters rather than only stripping them Outside the England, Scotland and Wales flag emoji — which are encoded as invisible tag sequences, and which broke Microsoft’s first attempt at this signature — these code points are rare enough to be a high-value anomaly.
Test your own pipeline rather than assuming Microsoft is explicit that implementations vary. Send yourself a message with an invisible tag character inside a word your rules match on, and see whether the rule still fires.
Apply the same normalization upstream of any AI that reads mail The control that defeats this evasion is the one that reduces prompt-injection exposure for assistants ingesting email. If you switched on an AI assistant over the mailbox this year, raise this.

One caution on indicators: the marketing platform’s tracking domains and sending IP range are shared with every legitimate customer of that platform, and Microsoft says plainly that the network block is not an indicator of compromise on its own. Use those to scope an investigation; do not block them.

If someone on your team already filled it in

No password was taken and no malware ran, so there is nothing to clean up in the usual sense. What was taken is a profile, and the response is about what happens next.

  1. Write down exactly what was entered. Revenue, requested amount, credit score, role, tenure, contact details. Every one of those is a fact the next attacker will use to sound informed.
  2. Tell the finance function the specific lie to expect. Not “be careful of phishing.” Tell them a call or email is likely coming that will correctly reference an application for roughly that amount, and that its purpose is to move money or collect banking details.
  3. Treat any inbound call about the application as hostile. The questionnaire ends by inviting a call. Anyone ringing about it did not get your number from a lender.
  4. Do not pay anything for a “faster” deposit. The advance-fee pattern the FTC describes shows up at exactly this stage: a processing, insurance or application fee payable before funds arrive.
  5. If a credit score or Social Security number went in, treat it as an identity incident too and work that in parallel. The business profile and the personal one get sold to different buyers.
  6. Report it. ReportFraud.ftc.gov, and if the lure used SBA branding, the SBA OIG Hotline.

If it turns out to be bigger than a form submission — credentials went in somewhere, or a payment moved — the sequencing matters more than the thoroughness, and we wrote the order to work in separately.

What to do now

Two things, both small. Ask whoever runs your mail filtering the normalization question and get an actual answer rather than a reassurance. And say the sentence out loud to whoever handles your money: we pick the lender, the lender does not pick us — then decide in advance who gets told when an unsolicited offer arrives.

If a link turns up and someone wants a second opinion, you can run the address through our free link checker. It will not resolve a marketing-platform tracking URL into a verdict on the business behind it, but it catches the cruder end of the range in seconds.

And if your team has never seen one of these under realistic conditions, the gap to close is not knowledge. Most people can list the red flags. The gap is that nobody has practiced the pause on a morning when the offer looks useful — which is the only morning it ever arrives.

Run the drill before the real one lands

ScamDrill sends your team realistic practice phishing emails — the funding offer, the vendor bank change, the “confirm your details” link — and coaches whoever clicks, privately. Nobody is named and nobody is graded. The point is that the pause becomes automatic. See how it works for small teams, or read the overview for organizations.

Start a free trial

Frequently asked questions

What is business funding phishing?

It is a phishing lure built around a loan, line of credit or advance funding offer, usually wearing the branding of a real lending program. The campaign documented by Fortra and Microsoft impersonated Small Business Administration line of credit programs, sending from hundreds of disposable finance themed domains. What makes it different from an ordinary credential phish is that it frequently takes no password at all: the landing page is a questionnaire asking for gross revenue, the loan amount wanted, personal credit score, role in the company and length of tenure, followed by a prompt to call a phone number.

Why does it matter if no password was stolen?

Because a password can be rotated on Tuesday afternoon and a profile cannot. A record saying your company bills roughly this much, wants roughly this much, is run by a person with this job title and this much tenure, and is actively seeking money right now stays accurate for months. Fortra assessed the objective as harvesting detailed business and financial information to enable highly targeted spear phishing later, which is why the questionnaire is better described as reconnaissance with a submit button than as a failed attempt to steal credentials.

My spam filter caught it. Are we fine?

Not necessarily, because the email is only one channel. The questionnaire ends by inviting the recipient to call for a faster response, and the profile it harvests is designed to make a later approach sound informed, whether that approach arrives by phone, by email or through a broker referral. A filter verdict tells you one message was stopped. It does not tell you whether anyone on your team already filled in the form, which is the question worth asking.

Why did the emails pass SPF, DKIM and DMARC?

Because nothing was spoofed. The mail was relayed through infrastructure associated with ActiveCampaign, a legitimate email marketing platform, sending on behalf of domains the operator genuinely controlled. Authentication confirms that a message came from where it claims, not that the sender is honest. The same relay also gave the campaign marketing grade IP reputation and rewrote every link to the platform's own click tracking domains, so the visible URL did not point at the finance domain at all.

Someone on my team filled in one of these forms. What now?

No credential was taken and nothing ran, so treat it as information loss rather than an intrusion. Write down exactly which fields were submitted, then warn your finance function specifically: expect a call or email that correctly references an application for roughly that amount, because sounding informed is what the harvested profile buys. Treat any inbound call about the application as hostile, refuse any upfront processing or insurance fee, handle a submitted Social Security number as a separate identity matter, and report it at ReportFraud.ftc.gov and to the SBA OIG hotline if SBA branding was used.

What is ASCII smuggling, and did it actually beat email security?

ASCII smuggling is the use of invisible Unicode characters, mostly from the deprecated Tags block at U+E0000 to U+E007F, to change what software reads without changing what a person sees. This campaign wedged one into the middle of words like funding so a keyword filter would stop matching them. It mostly did not work: Microsoft reports that over 99 percent of the messages were flagged anyway, by layers that never looked at those characters, including sender and URL reputation, machine learning classification and brand impersonation detection. It also backfired, because tag characters are almost absent from ordinary mail, so their presence is a high confidence anomaly signal.

What should we change in our email filtering?

Normalize before you match. Strip or fold invisible and non rendering code points, including the tag block, zero width space, zero width non joiner, no break space and soft hyphens, before any keyword, regex or signature logic reads the text. Alert on tag block characters rather than only removing them, since outside the England, Scotland and Wales flag emoji they are rare enough to be a useful anomaly. Test your own pipeline rather than assuming, because implementations vary. And apply the same normalization upstream of any AI assistant that ingests mail, since it reduces prompt injection exposure at the same time.