OQIRON
Secure your exchange account first
If there are any actual unknown positions or orders, prioritize account security by relying on the exchange’s official records. OQIRON customer service will never remotely request your private keys to check your account on your behalf.
- Immediately revoke any APIs suspected of being compromised on the exchange; do not simply remove the binding on the Oqiron page.
- Check exchange login records, API lists, open positions, standard orders, and conditional orders
- Change your exchange password and check your two-factor authentication, email, and device security
- Do not share your API Secret, passphrase, password, private key, or mnemonic phrase with anyone.
Prevent bots from continuing to create new risks
Initiate a bot stop only when it is safe to do so, and avoid performing the same operation on multiple pages simultaneously. After revoking the API, the bot will be prohibited from taking on new risks because it cannot verify private data; however, this does not mean that existing positions on the exchange have automatically disappeared.
Provide customer service with verifiable but non-sensitive information
Customer service will assist in verifying OQIRON ownership and records, but will never ask customers to send their secret credentials via chat tools.
- Customer ID, bot name, exchange, and approximate time of occurrence
- Screenshots showing on-page statuses, error messages, and screenshots that do not contain private keys
- Exchange public order ID or on-chain transaction ID
- Clearly indicate which actions were performed by me and which were not.
The sequence of exception handling determines whether the risk can be stopped from escalating as quickly as possible.
The top priority is always the exchange accounts that customers can directly control: revoke suspicious APIs, secure logins, and verify actual positions and orders. Simply contacting the platform without revoking compromised keys will allow attackers to retain access to the exchange.
Once your account is secure and stable, compile a timeline and reference numbers to help the platform determine which orders originated from OQIRON and which were placed manually or from unknown sources. A complete timeline is more valuable than sending a large number of unrelated screenshots; additionally, you must obscure any sensitive credentials in all screenshots.
After reading this, what should customers be able to do?
Truly understanding a knowledge article isn’t about memorizing a few terms, but about being able to make the right decisions based on actual page content and account status. Use the checklist below to verify whether you’ve grasped the key points.
- First, revoke any suspicious APIs on the exchange and secure your login credentials.
- Verify regular orders, conditional orders, and actual positions
- Record the time, public order number, and your own actions
- Contact customer service only through official channels; never send confidential credentials.
Frequently Asked Questions
These questions are directly related to the content of this article. Answers are based on current platform rules and actual operational standards; however, when it comes to packages, percentages, the scope of available features, or account status, the information displayed on the customer dashboard and official statements shall prevail.
- Will customer service ask me for my API Secret or mnemonic phrase? | No. Do not send your API Secret, passphrase, private key, mnemonic phrase, or password via online customer service, Telegram, WhatsApp, or any other chat platform.
- What Can You Do After Your Account Is Frozen? | A frozen account typically still allows you to log in and view information, but you will be unable to make withdrawals, start or stop trading bots, add, delete, or modify APIs, perform fund-related operations, or change subscriptions. A frozen account does not mean you have been blacklisted; please contact customer service following the data masking prompts to verify the reason.
- What information do I need to provide when contacting customer support? | Simply provide the page name, the time the issue occurred, the customer-visible status, and a screenshot that does not show any keys. For on-chain issues, you may provide the public transaction ID; do not send passwords, API secrets, passphrases, private keys, or mnemonic phrases.