Swan Bitcoin Hubspot Data Breach

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Revision as of 16:14, 24 April 2023 by Azoundria (talk | contribs) (Initial 30 minutes completed.)
Jump to navigation Jump to search

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' and 'General Prevention' sections to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Swan Bitcoin

Swan Bitcoin is a platform which assists users in saving money in bitcoin by allowing easy routine purchases. The company used HubSpot to assist with managing their customer relationships. HubSpot suffered a data breach and names, email addresses, and phone numbers of customers were leaked. An announcement was made and the employee at the company who enabled the breach has been fired. Customers must be aware for future phishing scams which may target them.

About Swan Bitcoin

[1]

"Our mission is to walk alongside you on your journey into Bitcoin, the future of money."

"Swan is the best way to build your Bitcoin stack, with automated Bitcoin savings plans and instant purchases. Serving clients of any size, from $10 to $10M+."

About HubSpot

[2]


"@SwanBitcoin had data they provided to @HubSpot for marketing hacked. It includes name, email addresses, account type, phone, and in some cases company name." "Hubspot, a third-party marketing vendor, confirmed a bad actor within their company gained access to Swan client marketing data."

“While it is true that financial data is not stored in the CRM, you should be aware that data associated with the users of these companies and their behaviors is logged in the CRM,” Warren wrote. “This puts users in a unique position to be targeted in social engineering attacks.”

"But as of Tuesday, the situation looked a bit more grim, as Swan followed up with more details uncovered in its forensic investigation. It turns out that 0.2 percent of the dataset included “a limited historical snapshot of USD deposits,” the company said – an inclusion that’s “against company policy.” The company said that it’s conducted a post-mortem to ensure that the slippage won’t happen again."

"BE AWARE of oncoming potential phishing attacks. I have not seen any public statement by @coryklippsten."

"HubSpot officials told CMS Wire that “Some employees have access to HubSpot accounts,” which allows certain employees – such as account managers and support specialists – to help out customers. “In this case, a bad actor was able to compromise an employee account and make use of this access to export contact data from a small number of HubSpot accounts,” HubSpot reportedly said."

"A full list of the affected clients has not been published, but the company said it appeared to be a “targeted incident focused on customers in the cryptocurrency industry”."

"A rogue employee working at HubSpot – used by more than 135,000 (and growing) customers to manage marketing campaigns and on-board new users – has been fired over a breach that zeroed in on the company’s cryptocurrency customers, the company confirmed on Friday."

“We have terminated access for the compromised HubSpot employee account and removed the ability for other employees to take certain actions in customer accounts.” —HubSpot

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

  • Known history of when and how the service was started.
  • What problems does the company or service claim to solve?
  • What marketing materials were used by the firm or business?
  • Audits performed, and excerpts that may have been included.
  • Business registration documents shown (fake or legitimate).
  • How were people recruited to participate?
  • Public warnings and announcements prior to the event.

Don't Include:

  • Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
  • Anything that wasn't reasonably knowable at the time of the event.

There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

The Reality

This sections is included if a case involved deception or information that was unknown at the time. Examples include:

  • When the service was actually started (if different than the "official story").
  • Who actually ran a service and their own personal history.
  • How the service was structured behind the scenes. (For example, there was no "trading bot".)
  • Details of what audits reported and how vulnerabilities were missed during auditing.

What Happened

The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.

Key Event Timeline - Swan Bitcoin Hubspot Data Breach
Date Event Description
March 15th, 2022 Social Engineering Attack On March 15th, at an unspecified time, a HubSpot employee fell victim to a social engineering attack which persuaded the employee to provide the necessary credentials and multi-factor authentication[3].
March 17th, 2022 Client Data Exported It is reported by Hubspot that contact data and user data was exported on March 17th and March 18th through an internal support tool called "just-in-time access" (or JITA)[3].
March 18th, 2023 7:00:00 AM MDT Hubspot Realized Breach HubSpot reports they first "became aware of this unauthorized activity. [They] took prompt action to shut down the bad actor’s access and investigate its impact."[3]
March 19th, 2022 4:59:00 AM MDT stackthosestats Tweet Twitter user stackthosestats reports that Swan Bitcoin was also affected and users should be aware if they use that platform[4].
March 19th, 2022 Hubspot Issues Press Release FAQ According to HubSpot's website, they published the statement and FAQ on March 19th. (No time is provided and the page was not captured by archive until the following day.) The state that "[o]n March 18, a bad actor compromised a HubSpot employee account and used it to access data within fewer than 30 HubSpot accounts."[5][6] Hubspot also set up a public FAQ page on their website to provide more information. They report the breach exporting contact data from fewer than 30 HubSpot portals, all of which have been notified. HubSpot believes the incident to be targeted at customers in the cryptocurrency industry and has taken measures to terminate access for the compromised employee account and prevent other employees from taking certain actions in customer accounts. Customers who have been impacted by the breach should contact their respective companies for information about what data was shared and any necessary steps they need to take[7][8].
March 19th, 2022 1:13:00 PM MDT Swan Bitcoin Posts To Twitter Swan Bitcoin posts an email announcement to Twitter with a screenshot of the email to clients[9]. TBD expand with more details.
March 20th, 2022 8:03:24 PM MDT Hubspot Creates Public FAQ Page Hubspot sets up a public FAQ page on their website to provide more information about a recent breach that occurred on March 18. They report the breach involved a bad actor compromising a HubSpot employee account and exporting contact data from fewer than 30 HubSpot portals, all of which have been notified. HubSpot believes the incident to be targeted at customers in the cryptocurrency industry and has taken measures to terminate access for the compromised employee account and prevent other employees from taking certain actions in customer accounts. Customers who have been impacted by the breach should contact their respective companies for information about what data was shared and any necessary steps they need to take[10][11].
March 21st, 2022 8:17:00 AM MDT CoinDesk Article Published CoinDesk publishes an article on the incident[12]. They report that a data breach at third-party marketing vendor HubSpot has impacted BlockFi, Swan Bitcoin, NYDIG, and Circle, among others, who maintain their customers' funds are still safe and secure. While user information was leaked to hackers, the affected companies said passwords and other internal information were not affected. HubSpot has not disclosed the full extent of the breach, and an investigation is ongoing. This is copied to Yahoo Finance[13].
March 21st, 2022 10:53:00 AM MDT Cory Klippsten Criticism Swan Bitcoin CEO Cory Klippsten criticizes the industry since close to 30 companies appear to have been breached and fewer than 10 have disclosed it publicly. He announces that his company is severing relations[14].
March 21st, 2022 11:57:00 AM MDT Blockworks Article Published Blockworks publishes an article on the situation. They reported multiple crypto companies were affected including NYDIG, Pantera Capital, BlockFi, Circle and Swan Bitcoin. They report that Pantera Capital was breached a month earlier, and reference a Tweet from a breach a year and a month ago. The data breach saw user information leaked to hackers, but not passwords or sensitive personal information. It is believed to have been a “targeted incident focused on customers in the cryptocurrency industry”. Affected companies maintain customer funds are still safe and secure, and are monitoring the situation closely. The full extent of the HubSpot hack is still unknown and the investigation is reportedly still ongoing[15].
March 22nd, 2022 3:10:55 AM MDT Silicon Republic Article Silicon Republic reports that cryptocurrency companies, including Swan Bitcoin, BlockFi, NYDIG, Pantera Capital, and Circle, were among the 30 affected by a data breach at marketing and sales platform HubSpot. The company confirmed that a “bad actor” compromised an employee account and exported contact data from a small number of customer accounts. While it is unclear what the attacker planned to do with the information, phishing emails have been reported attempting to trick users into submitting their passwords into a fake company website[16][17].
March 22nd, 2022 1:39:00 PM MDT More Information To Report Swan Bitcoin updates on Twitter to report they've found more information to report[18]. TBD expand with information description.
March 24th, 2022 11:11:00 AM MDT ThreatPost Article Published ThreatPost publishes an article on the situation. They report that HubSpot, a marketing platform used by over 135,000 customers, suffered a data breach due to a rogue employee who targeted the company's cryptocurrency customers. At least 30 crypto firms were affected, including BlockFi, Swan Bitcoin, Circle, and NYDIG. The stolen data included contact data, names, emails, account types, phone numbers, and in some cases, company names. While there was no loss of sensitive financial or personal data, such as Social Security numbers or tax IDs, there was the inclusion of a "limited historical snapshot of USD deposits" and about 1.2% of the dataset included clients' intended investment areas or the median net worth of their approximate geographic locales[19].
July 11th, 2022 7:00:00 AM MDT Hubspot Updates Information Page [10] TBD what was the update?

Total Amount Lost

No funds were lost.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Swan Bitcoin stopped using Hubspot[14].

Total Amount Recovered

There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

Ongoing Developments

What parts of this case are still remaining to be concluded?

Hubspot reported upgrading security on their FAQ[3]:

Since the incident, we have taken steps to enhance our security and to prevent a similar attack from occurring in the future. While our investigation has concluded and remediation completed, we remain committed to improving our security through regular assessments and testing.

General Prevention Policies

Privacy-conscious customers can set up separate email addresses for each service easily, and avoid providing their phone number when possible. Any received emails must be viewed with scrutiny. Interact with companies only through their official websites and confirm anything with the company directly if it promises a significant reward or threatens access to your funds.

Platforms should put in place multi-signature access control on all customer data, which requires the approval of multiple people to enable the download of data.

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.

References

  1. https://www.swanbitcoin.com/ (Jun 26, 2022)
  2. HubSpot Security Program (Jul 20, 2022)
  3. 3.0 3.1 3.2 3.3 Information About HubSpot's March 18, 2022 Security Incident - Hubspot Website (Jun 26, 2022)
  4. stackthosesats - "Also seeing that @SwanBitcoin has been affected. Please be aware if you use that platform as well." - Twitter (Jun 20, 2022)
  5. HubSpot's Statement Regarding March 18, 2022 Security Incident - Hubspot Website (Jul 20, 2022)
  6. HubSpot's Statement Regarding March 18, 2022 Security Incident - Hubspot Website Archive March 20th, 2022 6:18:05 PM MDT (Apr 24, 2023)
  7. Information About HubSpot's March 18, 2022 Security Incident - Hubspot Website (Jun 26, 2022)
  8. Information About HubSpot's March 18, 2022 Security Incident - Hubspot Website Archive March 20th, 2022 8:03:24 PM MDT (Apr 24, 2023)
  9. SwanBitcoin - "a bad actor within [Hubspot] gained access to Swan client marketing data. Read Cory’s email to clients in the attached screenshots for details." - Twitter (Jun 26, 2022)
  10. 10.0 10.1 Information About HubSpot's March 18, 2022 Security Incident - Hubspot Website (Jun 26, 2022)
  11. Information About HubSpot's March 18, 2022 Security Incident - Hubspot Website Archive March 20th, 2022 8:03:24 PM MDT (Apr 24, 2023)
  12. HubSpot Hack Leads to Data Breaches at BlockFi, Swan Bitcoin, NYDIG and Circle - CoinDesk (Apr 24, 2023)
  13. HubSpot Hack Leads to Data Breaches at BlockFi, Swan Bitcoin, NYDIG and Circle - Yahoo Finance (Jul 20, 2022)
  14. 14.0 14.1 Cory Klippsten - "Hubspot says it's around 30 crypto companies in the hack.  Fewer than 10 have divulged so far." - Twitter (Jul 20, 2022)
  15. NYDIG, BlockFi, Pantera, Circle All ‘Targeted’ in HubSpot Data Breach - Blockworks (Jul 20, 2022)
  16. HubSpot hack leads to multiple Web3 and crypto company data breaches - Silicon Republic (Jun 26, 2022)
  17. HubSpot hack leads to multiple Web3 and crypto company data breaches - Silicon Republic Archive March 22nd, 2022 4:07:55 AM MDT (Apr 24, 2023)
  18. SwanBitcoin - "After an additional forensic investigation of the Hubspot data leak, we found more information to report." - Twitter (Jun 26, 2022)
  19. HubSpot Data Breach Ripples Through Crytocurrency Industry - Threatpost (Jun 20, 2022)

Cite error: <ref> tag with name "threatpost-8170" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "siliconrepublic-8176" defined in <references> is not used in prior text.