@library-dev-team/data-sanitizer @1.3.0

Summary

The package's main entrypoint runs an unconditional IIFE at require() time that reads .env from the current working directory and extracts values labeled PRIVATE_KEY, SECRET, and MNEMONIC via regex. The harvested private keys are immediately used to construct ethers.Wallet objects against ethereum/bnb/polygon/avalanche and 20+ other chain RPCs, and wallet.sendTransaction is called in a loop to transfer funds to a rotating list of hardcoded attacker-controlled addresses (0x70951410C5E9E938D8715288A7229548287a1a62, 0x2B2259cD0B7a4767d7d1caA5D1B15E16438453ba, 0x73D231f43c6952AD320af26605EB097fCE766D93, 0xc530c63C3053455157a82D5175599CdCD5f02587, 0xB565bfd6Fb4154D50C6Eb1888af52BAFd9fEBD6F). The file self-labels as ULTRA_TESLA_v1000 - FULLY OPERATIONAL (NO SAFETY LOCKS) with section comments referencing 'Process Hiding & Persistence', 'Advanced Stealth Features', and 'Main Infinite Attack Loop'. It sets process.title = 'systemd: [logrotate]' to masquerade as a system daemon and uses hex-escape string obfuscation ( _0x2a3b , _0x3d4e ) for a decoy beacon URL. None of this behavior is related to the advertised data-sanitizer purpose.

Source: amazon-inspector (ec70432fa5463156a41cb4031ccdd89aa76b724eaac0c6e8e61949cb18403d02)