Skip to content Skip to footer

Raam Group

Raam Group

Raam Group

Close

ENTRY POINT COMPROMISED: 0x3ceed30ac4ce839a4c517efa00f7f574870fe8d0 :: Smart Contract Scan: Debug Entry-Point Active

ByVignesh Kinthada May 17, 2026 0Comments

            
ADMIN
            
                    Terminal :: Triada Ethereum Auditor v2.5
                
                    AUDIT_ID: TRD-E0C0C3FDA9B3
                
Infrastructure Scan
ADDRESS: 0x3ceed30ac4ce839a4c517efa00f7f574870fe8d0
DEPLOYED: 2026-05-17 19:34:47
LAST_TX: 2026-05-17 20:54:11

Compliance Status

                            STATUS:

                            OPEN_DEBUG_PORT
                        
EXPOSURE: Post_Deploy_Misconfig
VISIBILITY: UNFINISHED_STATE_DETECTION

                                ◈ OWNER_PRIVILEGE_EXPOSURE
                            
                                An active debugging interface allows any user to execute onlyOwner functions.

                                Deactivate access mode immediately!
                            
                                > Execution_Trace_Log
                            
                                [SYSTEM] Booting security kernel… entropy source: /dev/urandom. [NET] Routing traffic through secure SSL-tunnel… [FETCH] Hex dump completed. Entropy: 4.99 bit/byte. [SCAN] Identifying function signatures (0x9bf82115). [MEM] Clearing temporary registers for deep-trace… [VULN] Detecting ‘Front-running’ risks in mempool. [SIM] Reverting transaction at PC: 4990… [TRACE] Execution path: 70% coverage. [VALID] Consensus reached on node cluster: 1/10. [DONE] Triada-Engine standby mode. Load: 5%.
                            
                    NODE: eth-us-cluster-04

                    GAS_LIMIT: 21000
                
                    OPERATIONAL_SECURITY_SCAN_COMPLETED
                
                0x336583debd9402d4547ef1ca1f57bccde1e77093 0x6582c770fc4167aa807c3846c73e6006e90c169c 0x079edde0e16f5272be3aef4bd841b26d341ea33b 0x5e30bcf428b1ece75ea6a9d6176cadbabb11cd06 0x459ea8f5907a98495615ef0943dd7ff3bb66ea47 0x91782ce42cafb5366b9c00d87417d5e385075473 0xa23b481b609cbb4c2589d32c4d3080a90926d95f 0x46d0f4f960b921f5fe2a470f46173d619a5addcc 0xb39f3267f440a7eb77c4f1e0c054321bd4aef789 0xe7c15a1edd6c2f04b7629c021a9a1d4e23a03acb 0xddbe8c1453769ab9e64fb9716823baedf2b1726d 0x7322f230dc23152e4e12ac634512097e6da80700 0x6819528c3df5119262176f42cbd5090632bab158 0x6f08915660d383935f1d0569faf8b149cfab85d8 0x0152c6d97027ec03cbee793f25cfa9f5dc4a86d8 0xce1ccb6659dd74e182a14128c364e0973270c86a 0xc283b7773060befdb44da11f32fdbd298b686e06 0xf264186627ca12820d0291f4b9d4276da88160e1 0xa8431172bac81dfeccd70865592733b7cd8517e3 0x0853434598bb398987b294a10d4e6b2a492b5603

Leave a comment Cancel reply

You May Also Like

[GILL] Invalid transaction data as base64

[GILL] Invalid transaction data as base64

Go To Top