General Bytes Bitcoin ATM Zero-Day Exploit

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' section 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.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

General Bytes Logo/Homepage/ATMs

General Bytes is one of the most well-known bitcoin ATM companies globally. On March 17th, 2023, a zero-day exploit was found and exploited in their Java-based system. This was used by the attacker to steal 56.23311638 BTC among other assets. There is no suggestion that any funds have been recovered, although the company is compensating victims from their own funds.

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

About General Bytes

"Bitcoin and Cryptocurrency ATMs" "Discover the full range of the World's best-selling Bitcoin ATMs! One-way and Two-way Bitcoin ATMs working on our platform are synonyms for reliability, scalability, attractiveness, manageability, and profitability."

"We offer the industry's broadest range of Bitcoin ATMs, including one-way and two-way models. Our cloud-based management app, CAS, helps clients easily manage their fleets of Bitcoin ATMs. GENERAL BYTES is the global leader in Bitcoin ATM manufacturing, with 11,000+ ATMs operated worldwide in 60+ countries. Our modular design meets global AML/KYC requirements, and our seamless integration simplifies commission, fee, and compliance management. Our machines support instant Bitcoin purchase/sale via Lightning technology. Watch this video to learn more about us!"

General Bytes "is based in Prague and, according to its website, has sold over 15,000 Bitcoin ATMs to purchasers in over 149 countries all over the world."

"It was understood that the hack led to at least 56 Bitcoin, worth over $1.5 million at current prices, and 21.82 Ether, $37,000 at current prices, being deposited into wallets connected to the hacker."

“We have taken immediate steps to prevent further unauthorized access to our systems and are working tirelessly to protect our customers,” General Bytes said in a statement.

"Along with the reimbursement for affected customers, the ATM manufacturer has also said they are encouraging all customers to migrate to a self-hosted server installation, where they can effectively secure their server platform using VPN."

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 - General Bytes Bitcoin ATM Zero-Day Exploit

Date	Event	Description
March 17th, 2023 3:24:03 AM MDT	First Bitcoin Transaction	The first bitcoin theft transaction on the blockchain.
March 17th, 2023 5:07:53 AM MDT	Last Bitcoin Transaction	The final bitcoin theft transaction before the system is potentially shut off.
March 18th, 2023 2:42:00 PM MDT	Twitter Post	General Bytes posts on Twitter to notify customers about the security incident and bulletin.
March 21st, 2023 8:51:19 AM MDT	Attacker Funds Moved	The attacker moves their bitcoin to another wallet.
March 27th, 2023 10:57:37 PM MDT	CoinTelegraph Article	CoinTelegraph reports on the issue.

Technical Details

This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

Total Amount Lost

The total amount lost has been estimated at $1,500,000 USD.

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

Crypto addresses used by attacker ADA = 0x7A0E7D41658F409C11288E0a2988406f2186A474 AQUA = 0x7A0E7D41658F409C11288E0a2988406f2186A474 ANT = 0xD5173d215551538cebE79C4e40A4C54Fb751DD83 BAT = 0x3d1451bF188511ea3e1CFdf45288fD53B16FE17E BCH = 0xD5173d215551538cebE79C4e40A4C54Fb751DD83 BTBS = 0xD5173d215551538cebE79C4e40A4C54Fb751DD83 BTC = bc1qfa8pryacrjuzp9287zc2ufz5n0hdthff0av440 BTX = 0x7A0E7D41658F409C11288E0a2988406f2186A474 BUSD = 0x7A0E7D41658F409C11288E0a2988406f2186A474 DAI = 0x7A0E7D41658F409C11288E0a2988406f2186A474 BIZZ = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 DASH = Xi4GstuqKFTRo3WB6gFpPnB6jiWtLSHJDj DGB = dgb1qgea3hzw62zl6req06k708swtv5xc53sdp85jzn DOGE = DN1bKoV7BbuYBeysnYNT8EFj8BGTSeyLCc ETC = 0x8A9344be2BA8DeAA2862EAb0Aab20C7cC36c432a ETH = 0xD5173d215551538cebE79C4e40A4C54Fb751DD83 EGLD = erd1w7n54rlzrxe6jl8xpmh0de4g9jhc028zeppsjdme9g45gsnhw53s4vhgsg EURS = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 FTO = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 GRS = grs1qhckdwm8dqt8pfdu2d6e649qs5jrqn6sslzlyhw GQ = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 HATCH = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 HT = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 JOB = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 LMY = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 LTC = ltc1qvd5usunrpgsynyeey9n46xucy7emk62ycljl0t MKR = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 NANO = nano_1rrqx4esqbfuci7whzkzms7u4kib8ojcnkaokceh9fbr79sa4a36pmqgnxd4 NXT = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 PAXG = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 REP = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 SHIB = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 TRX = TDjFvfcysNGaxnX7pzpvC6xfSmCC5u8qgr USDS = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 USDC = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 USDT = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 USDTTRON = TDjFvfcysNGaxnX7pzpvC6xfSmCC5u8qgr VIA = via1quynq6wweqz0pk9wygv82qg83tk5zu47yqweht5 XRP = rDkoXVLChaDvc8SHFoTNZEDzcbtFNwF977 ZPAE = 0xAE0aC391b8361B5Fc1aF657703779886a7898497 XMR = 426FQDKF9rbHZLbNgisRKU2m2CVfnoNpFL7ZsAoDQBHP1eRDUKaj64zDtnFychJqSg1W6eskoFqdkG4gX8BSvWvkQr8oxVc

IP addresses used by attacker 123.204.4.202

172.104.237.25

172.104.237.25

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?

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.