SIREN contract has no audit + 88.5% control, is this really a project or just an easy way to run away?

Recently, SIREN's price surged from 0.7 to over 1.8, then fell back and fluctuated sideways, sparking intense community discussion.
I carefully examined the contract code (0x997a58129890bbda032231a52ed1ddc845fc18e1) and found several issues:
The contract has not undergone a public audit.
The code is a standard OpenZeppelin ERC20 template + Ownable permission control, with an added _mode switch (which can restrict transfers at any time). It has been verified on BscScan but lacks reports from well-known audit firms (CertiK, PeckShield, SlowMist, etc.). The project team also hasn't published any audit links on their official website or social media.
Permission design facilitates market manipulation
The owner can transfer ownership at any time and switch transfer modes (MODE_TRANSFER_RESTRICTED can directly prohibit transfers). This isn't uncommon in meme projects, but combined with on-chain data, it appears particularly sensitive.
On-chain control is highly centralized
According to EmberCN and other on-chain monitoring tools, a single entity controls about 88.5% of the supply (approximately 644 million tokens). Among them, 48 addresses have been rapidly accumulating recently, some traceable to addresses related to DWF Labs. Dead addresses hold 27%+ and have barely moved, still part of the "fake burn" narrative.
Market behavior is highly consistent
Repeated cycles of "dump → violent rally → pullback and oscillation" occur, with large buy orders and small fund inflows repeatedly appearing as false signals. During rallies, trading volume spikes, but genuine new buying is weak, making it look more like the manipulators are creating liquidity to sell off. $SIREN