Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Sichere ProgrammierungAutomating Bug Reports with Tally and Make(22.09.2026 um 22:44 Uhr)
Sichere ProgrammierungHTB - Forest(22.09.2026 um 22:49 Uhr)
Sichere ProgrammierungYour Ports Are Lying About Your Business(22.09.2026 um 22:52 Uhr)
Sichere ProgrammierungOLTP vs. OLAP: Understanding the Foundation of Modern Data Systems(22.09.2026 um 22:54 Uhr)
Sichere ProgrammierungYour AI Meeting Assistant Is Taking Notes. Who Is Doing the Work?(22.09.2026 um 22:57 Uhr)
Sichere ProgrammierungDebuggear se va a acabar(22.09.2026 um 23:03 Uhr)
Sichere ProgrammierungAutomating Bug Reports with Tally and Make(22.09.2026 um 22:44 Uhr)
Sichere ProgrammierungHTB - Forest(22.09.2026 um 22:49 Uhr)
Sichere ProgrammierungYour Ports Are Lying About Your Business(22.09.2026 um 22:52 Uhr)
Sichere ProgrammierungOLTP vs. OLAP: Understanding the Foundation of Modern Data Systems(22.09.2026 um 22:54 Uhr)
Sichere ProgrammierungYour AI Meeting Assistant Is Taking Notes. Who Is Doing the Work?(22.09.2026 um 22:57 Uhr)
Sichere ProgrammierungDebuggear se va a acabar(22.09.2026 um 23:03 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

Shield Every Transaction

Today i have found the new strategy of how can i write my own custom smart contracts to analyze the transactions more efficiently. Back then i was analyzing using simple server-side logic and using regex to just read the bytecode of the…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Today i have found the new strategy of how can i write my own custom smart contracts to analyze the transactions more efficiently.

Back then i was analyzing using simple server-side logic and using regex to just read the bytecode of the smart contract user wants to analyze.



We were using etherscan api to fetch the bytecode and i make my regex logic to read it and detect any malicious pattern.






Example:



If the smart contract of any new coin is not verified on the etherscan site my simple server side logic simply returns ABI not found.

If the scammer made the smart-contract and added a malicious logic for instance For adding a user who interacts with scammer smart contract is added to blacklist and never withdraw token/coin/real money so my logic is simply detecting the names of the function scammer might have created.

So my regex logic is just looking at the names in the bytecode of smart contract "blacklist" and similar to that.

But what if **Scammer is using something like




UniCORN

** to dodge the audit of smart contracts.




so in that case my TxShield platform did not catch it, so i have been researching for the past 1 week and i have found a solution.






THE SOLUTION I FOUND:



Now to detect the fake names and ditching my naive REGEX logic, I write my own custom solidity smart contract to bypass this SCAM,

now in my smart contract logic I have brute-forcing the write/read bytes selectors of the BLACKLIST_METHODS which catches the most of the scams instantly, because it's no longer detecting the hard-coded names, it's detecting the pattern of bytes on which now scammer names whatever the function name when this function is executed in our TxShield's sandbox smart contract logic, it detects => is it storing any user address or not in some king of list/mapping.






The Teqnique:



This technique is called Phantom Contracts we are running our own custom smart contracts and not deploying we are just using our Infura to call the built-in method calleth with parameters and boom we have run our own smart contracts.






Benefits of phantom contracts:



You don't need to deploy your smart contract.

It's security driven no sharing of your source code.

You can your smart contract and directly use them inside your server-side code.






The Quesiton for you guys



Would you use this Phantom Contracts Techniques in your own code?

Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Shield Every Transaction

Thematisch verwandte Begriffe: Shield, Every, Transaction · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-82000 | Adobe Experience Manager Forms JEE is affected by a Server-Side Request …
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick