explaingit

baunigregerander/flasher_usdt_eth_btc

23PythonAudience · general

TLDR

A local Windows tool that patches wallet software to display a fake cryptocurrency balance without touching the blockchain. Widely associated with cryptocurrency fraud used to deceive counterparties into believing a payment was received.

Mindmap

mindmap
  root((flasher-usdt-eth-btc))
    What it claims
      Local balance spoofer
      Fake transaction history
      No blockchain access
    Targets
      MetaMask
      Trust Wallet
      Electrum
    Config options
      Token network
      Balance amount
      Persistence toggle
    Warnings
      Associated with fraud
      Deceives counterparties
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Display a spoofed cryptocurrency balance inside a local wallet app such as MetaMask or Trust Wallet without making any real transaction.

USE CASE 2

Inject a fake transaction history alongside a fake balance so the display looks more convincing on a local machine.

Tech stack

PythonWindows

In plain English

This is a Windows tool that claims to modify the balance display inside cryptocurrency wallets on a local machine, making them show a custom USDT, BTC, ETH, or other token balance that does not reflect the actual on-chain holdings. The README describes it as a "client-side injector" that patches local storage, memory, or cached API responses inside the wallet software without connecting to any blockchain or accessing private keys. The tool targets browser extension wallets such as MetaMask and Trust Wallet by hooking into developer tools bridges or local storage. For desktop wallets like Electrum and Exodus it claims to use memory patching or library injection. For node-level clients such as Bitcoin Core or Geth it intercepts local RPC responses or cached files. In all cases the changes stay on the local machine and are described as reversible. A configuration file lets users set a target balance amount, choose a token network (ERC20, TRC20, or BEP20), and toggle whether the fake balance persists after the wallet restarts or disappears on exit. A separate option injects a fake transaction history alongside the spoofed balance. The tool ships as a single executable with no installation required and works offline. The project's own topics include terms like "fake-btc-transaction" and "flash-btc-software," and its stated purpose is to display balances that do not exist on any blockchain. Tools of this type are widely associated with cryptocurrency fraud, used to deceive counterparties in peer-to-peer trades or escrow arrangements into believing a payment was received when it was not. The README carries no security-research or testing disclaimer.

Copy-paste prompts

Prompt 1
What warning signs should I look for to detect whether a cryptocurrency wallet balance has been spoofed locally rather than reflecting real on-chain holdings?
Prompt 2
How does memory patching or local storage injection work in browser extension wallets like MetaMask, and what defenses exist against it?
Prompt 3
Explain how a tool that intercepts local RPC responses in a node client like Bitcoin Core could make the wallet display a balance that does not exist on the blockchain.
Open on GitHub → Explain another repo

← baunigregerander on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.