Scoutinternal

Unsolicited SEO, Guest Post, and Marketing Spam Submitted to BitGo Support

Unsolicited SEO, Guest Post, and Marketing Spam Submitted to BitGo Support

Problem

BitGo support receives a high volume of unsolicited commercial emails submitted as support tickets. These messages offer SEO services, guest post placement, backlink building, website development, mobile app development, sponsored article publication, and similar marketing/advertising pitches. They are not legitimate customer support requests and contain no actionable BitGo product issues. They arrive at support@bitgo.com and are auto-created as Salesforce cases.

Diagnostics

  • Check the ticket subject line: Common indicators include phrases such as "guest post," "backlinks," "DA," "traffic," "SEO," "sponsored post," "website designing," "app development," "link building," "link insertion," "Google rankings," or offers to publish articles on bitgo.com or blog.bitgo.com.
  • Check the sender address: The sender is typically an external marketing agency, SEO freelancer, or outreach specialist — not a BitGo customer or known business contact. The email domain will not match any known BitGo client domain.
  • Check the ticket body: The message will typically list third-party website URLs with Domain Authority (DA), traffic stats, or page authority (PA) metrics, and/or offer paid services. There is no mention of a BitGo wallet, transaction, coin, API issue, or any BitGo product feature.
  • Check for any prior case history: The sender will have no prior legitimate BitGo support interactions or associated BitGo account.
  • Distinguish from phishing: These spam tickets are commercial solicitations, not phishing attacks. They do not impersonate BitGo, request credentials, or contain malicious links targeting BitGo users. If a message does impersonate BitGo or request credentials, escalate per the phishing/security procedure instead.

Resolution

Scenario: guest-websites-traffic-sites#unsolicited-marketing-spam

Trigger: The inbound ticket is an unsolicited commercial solicitation (SEO, guest posting, backlinks, web development, app development, sponsored content, advertising) with no relation to any BitGo product or customer issue.

Signals: guest post, backlinks, DA, traffic, SEO, link building, link insertion, sponsored post, website designing, app development, Google rankings, guest posting websites, press release, dofollow link, organic traffic, web development, mobile app

Steps:

  1. Confirm the ticket contains no legitimate BitGo support request by reviewing the full message body. Verify there is no mention of a BitGo wallet, transaction, coin, API endpoint, or account issue.
  2. Do not engage with the sender's commercial offer. BitGo does not purchase guest posts, backlinks, SEO services, or sponsored article placements through the support channel.
  3. Close the ticket without further action. No substantive reply is required.
  4. If an auto-reply was already sent (e.g., the generic "Thank you for reaching out to us… please provide us with more details" template from support@bitgo.com), no follow-up is needed — the sender's lack of a legitimate issue means no further conversation will develop.
  5. If the same sender or agency submits repeated spam tickets, note the sender domain for potential email filtering by the IT/email operations team.

Notes: - Some tickets in this cluster were auto-responded to with a generic BitGo Technical Support template asking for more details. This is an undesirable outcome — these solicitations should be closed, not engaged with.

  • A small subset of tickets reference publishing content on bitgo.com or blog.bitgo.com specifically (e.g., "Article Publication on your website - bitgo.com," "Guest Post Order for blog.bitgo.com," "What is Guest Posting / Link insertion / Prices on your website - https://www.bitgo.com/"). BitGo does not accept paid guest posts or sponsored content via the support channel.
  • These are distinct from phishing attempts. If a message impersonates BitGo or attempts to harvest credentials, follow the phishing escalation process instead.
  • This cluster represents a very high volume: approximately 3,667 tickets in the dataset.

"From: support@bitgo.com … Thank you for reaching out to us. We understand your concerns and we are here to assist you. In order to address the issue you are facing, please provide us with more details so we can better assist you." (ticket #298454)

"From: support@bitgo.com … Thank you for reaching out to us regarding the opportunity to publish a paid article on our website. We appreciate your interest in collaborating with us. In order to proceed further, please provide us with more details about the article and how it aligns with the content of our website." (ticket #299871)

"What is Guest Posting / Link insertion/ Prices on your website - https://www.bitgo.com/ Kindly send me the best collaboration price." (ticket #21945)

Related

  • security-call-outs — Distinguishing spam from phishing; if a message impersonates BitGo or requests credentials, the phishing procedure applies instead of simple spam closure.
  • none identified for additional direct matches; this cluster is entirely non-product spam.