Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Cisco Talos screenshot of a Dell order-received email that embeds "Confirmed Order," "Helpline 808 232 6397" and "Call Our Sales Team" in the Ship To and Bill To fields for a Microsoft Project Standard 2024 order totaling $736.09.
Screenshot: Cisco Talos, Dell order notification used in a trusted-pipeline campaign, Oct 21, 2026 (fair use).

Detection

Cisco Talos Says Attackers Are Stuffing Helpline Numbers Into Real Staples and Dell Order Emails and Using Registration Forms and Bounces as Trusted Delivery

Talos says abuse of more than 25 legitimate platforms in the past year now includes commerce order pipelines that pass DKIM and DMARC while embedding attacker phone numbers, registration workflows that reflect hostile strings into welcome mail, and delivery-status reports that carry WeTransfer-style file-sharing lures inside the bounce.

Ava Okello, DetectionLondon5 min read

LONDON - Attackers are no longer limited to lookalike domains when they need a trusted inbox, Cisco Talos said on Oct. 21. They are writing their content into fields that legitimate platforms then render into order confirmations, welcome messages and delivery-failure reports that already pass sender authentication.

"Legitimate infrastructure has become a powerful delivery mechanism for attackers, carrying the inherent trust they once had to build," Talos wrote. The team said it has observed abuse across more than 25 distinct collaboration, productivity, file-sharing, survey, payment and AI platforms in the past year, building on earlier research into software-as-a-service notification pipelines.

Order notifications that pass authentication

Talos analyzed two order notification campaigns that abused Staples and Dell transactional email pipelines and together accounted for roughly 1,400 messages. The malicious element was not a forged outer sender. It was content inside fields that normally hold shipping or billing information, used to create urgency around a high-value purchase and push the recipient to an attacker-controlled phone number.

One message appeared as a Staples order confirmation from support@orders.staples.com with the subject "Here's your Staples order #9939818875. Thanks for shopping with us." The body listed an Apple iPad purchase totaling $455.81. Embedded in the order details were "Helpline 806 283 7712," "Order Confirmed" and the Staples corporate address. Headers showed DKIM alignment for orders.staples.com and a DMARC pass for the visible Staples domain, Talos said.

Cisco Talos screenshot of a Staples order confirmation email for an Apple iPad totaling $455.81 that embeds Helpline 806 283 7712 and Order Confirmed in shipping and billing fields.
Screenshot: Cisco Talos, Staples order notification, Oct 21, 2026 (fair use).

A second campaign used a Dell order-received message from received@order.dell.com with the subject "We have your order | Dell Purchase ID: 2009829958247." The body listed Microsoft Project Standard 2024 for $736.09. The Ship To and Bill To sections included "Confirmed Order," "Helpline 808 232 6397" and "Call Our Sales Team." Authentication results showed DKIM and DMARC passing for Dell-related infrastructure, Talos said.

"The desired user action was a phone call," Talos wrote. Once the victim moved from email to voice, the attacker could continue with social engineering, payment manipulation, credential theft or remote assistance fraud. Talos said the campaigns illustrate the same platform-as-a-proxy trust failure described in its earlier SaaS research: the attacker supplies the intent, while the trusted system performs the delivery.

List bombing and bounce abuse

Beyond commerce, Talos said a subset of list bombing now carries malicious content rather than only flooding an inbox. Attackers submit a victim's address to public registration or profile forms and place a "hostile string," such as a cryptocurrency-themed lure, in fields meant for a name, company or title. When the platform reflects that input into a welcome or verification email, the message arrives with the platform's reputation and can pass standard authentication checks.

Cisco Talos screenshot of a registration or profile notification that reflects attacker-controlled content, including a Coinbase Card lure and an Activate account button, inside a trusted platform email.
Screenshot: Cisco Talos, registration field reflection used as content delivery, Oct 21, 2026 (fair use).

A third vector moves the abuse into the mail system itself. Delivery status notifications, or bounces, may include original headers, body fragments, URLs, attachments or an encapsulated copy of the failed message. In one example Talos observed, a mail delivery system notification carried a WeTransfer-themed file-sharing lure. "The administrative wrapper made the message look like routine mail-system noise, while the nested content asked the recipient to engage with what appeared to be a file transfer workflow," the researchers wrote.

Cisco Talos screenshot of a Mail Delivery System undelivered-mail notice that contains a WeTransfer-themed "Get your files" lure and download link inside the bounce.
Screenshot: Cisco Talos, bounce carrying a file-sharing lure, Oct 21, 2026 (fair use).

Talos said opportunistic backscatter can forge the victim as the envelope sender so a later delivery failure returns attacker content, and that intentional bounce abuse can trigger a failure from a controllable sending context. From the mailbox, both can look like a legitimate delivery report wrapping a phishing payload.

What detection teams should change

  • Treat SPF, DKIM and DMARC as necessary but not sufficient. Talos said those controls answer where a message came from, not whether the rendered fields make business sense.
  • Inspect fully rendered transactional content, including HTML, text, URLs, personalization fields and nested MIME objects, not only the outer sender or template.
  • Flag order notifications that contain unexpected phone numbers, support instructions, cancellation language or high-urgency wording in shipping, billing or note fields.
  • For delivery reports, recursively parse DSN containers, extract returned message fragments and run the same phishing, malware and URL analysis used on ordinary mail.
  • Platform owners should validate any user-controlled value before storage and again before rendering into email, rejecting or flagging phone numbers, URLs, markup and urgent support language in fields where they do not belong.
  • Correlate order notification content with account history, payment state, shipping context and known support channels before treating the message as a routine receipt.

Sources:


Ava Okello covers detection engineering and SOC operations for SOCtember from London.

Related stories

Detection desk