Security Update: LAB Terminal
We identified a security incident involving a third-party integration used by the legacy LAB Terminal backend. Wallets created in or imported into Terminal were exposed, and unauthorized transfers have been confirmed from some of them, totaling $129,986 as of 08.10.
All verified losses will be compensated in full.
Details below.
The legacy Terminal backend has been fully shut down. This stops any new exposure, but it doesn't secure wallets that were already exposed, so please follow the steps below.
The current LAB App runs on separate infrastructure and is not affected by this incident.
Protect your remaining funds
Treat every wallet created in or imported into LAB Terminal as compromised:
• Stop using it and don't send any funds or tokens to it.
• Move any remaining assets to a brand-new wallet created with a new seed phrase.
• If you imported an existing wallet into Terminal, this applies to every chain and account that uses that seed phrase, in any wallet app.
• Don't claim upcoming LAB allocations or vesting to a Terminal wallet. Allocations linked to affected wallets are paused and will be sent to a new address after verification.
Compensation
LAB will compensate the full USD value of verified losses from this incident, calculated at the time of the unauthorized transfer and paid in USDT.
We've started contacting users with confirmed losses through the official LAB Terminal bot, http://t.me/LAB_Trading_bot, with instructions for receiving compensation.
If you believe you were affected but haven't received a message, contact us at https://t.me/lab_global_chat.
Beware of scammers
We will never ask for your seed phrase or private key, or ask you to connect a wallet or sign anything.
We're sorry this happened and understand how serious it is for everyone affected. Security has always been a priority for LAB, and this incident only reinforces the need to keep raising that standard.
We've completed our investigation and are in direct discussions with the providers involved about reimbursing LAB for the costs of this incident. Compensation for affected users is separate and doesn't depend on these discussions.