Use this ACE66 scam guide when a person claiming to be staff asks for a deposit, sends a payment link or pressures you to act before you can verify the message.
Recognise the approach
Treat an unexpected staff message as unverified until you check it elsewhere
A fake staff message usually creates urgency, moves the conversation away from a route you know and asks for money, secrets or access before independent verification.
The approach may begin with a WhatsApp, Telegram, SMS, social-media message or call from someone displaying an ACE66 name or image. The sender may say your account needs an immediate deposit, a payment recipient has changed, a withdrawal is locked or a promotion will expire. They may know your username, recent activity or another detail. Leaked, guessed or previously shared information can make a message sound personal, so knowledge of one detail is not proof of employment.
Look at the sequence rather than the polish. An ACE66 fake staff scam may start with friendly help, then add a deadline, threat or special exception. The sender may discourage you from opening the usual site, insist that only this chat can solve the issue or ask you to keep the instruction private. A professional profile picture, branded background, copied notice or screenshot can be created or reused by anyone.
Do not decide that every unusual message is definitely fraudulent. Decide that it is not verified. That distinction gives you a safe next step: end the conversation, open the ACE66 route you already know without using the message, and ask the support channel reached there whether the exact instruction is genuine. Until that check is complete, do not pay, approve a banking request, upload a document or reveal a code.
This page is narrower than a general account-security guide. It focuses on ACE66 staff impersonation, fake customer service, false deposit instructions and the first response after exposure. Use the account-protection and official-link Guides for deeper password, device and hostname checks.
Before you reply
Freeze the conversation without deleting the evidence
Stop typing, clicking and paying
Do not argue with the sender or ask them to prove the ACE66 claim through the same chat. A scammer controls everything shown in that conversation.
Do not call the number in the message
Caller ID and messaging profiles can be copied or spoofed. A callback to the supplied number only returns you to the unverified person.
Capture the message before blocking
Save the visible sender identifier, date, time, request, link, QR code and receiving details. Do not forward an active ACE66 scam link to friends.
Open a trusted route yourself
Use a bookmark or type the ACE66 address you previously verified. Do not paste the sender's shortened link, scan their QR code or use a search advertisement as a shortcut.
Use a clean device if you installed or approved something
If the sender gained screen sharing, remote control or suspicious app access, stop using that device for ACE66, email and banking until you have contained the risk.
Do not send a small test deposit
A small ACE66 transfer still gives money and transaction information to an unverified recipient. Verification must happen before any amount is sent.
Independent identity check
Verify the instruction outside the conversation that delivered it
Write down the exact claim
Record what the person says their ACE66 role is, why payment is requested, the amount, deadline, recipient and what they say will happen if you refuse. Do not add guesses.
End the unverified session
Do not let the sender guide the verification. Leave the call or chat so the person cannot answer on behalf of the real ACE66 support route.
Enter through a route you verified earlier
Open the ACE66 page or account independently. If you need to check a hostname, compare every character before entering login details.
Start a fresh support conversation
Use the support entry displayed inside that independently opened ACE66 route. Explain that you received an unsolicited request and provide a redacted summary, not your password or OTP.
Ask a question that can be checked
Ask whether ACE66 issued that exact instruction, amount, payment purpose and recipient at that time. A vague question such as 'Is this person real?' may omit the dangerous part of the request.
Do not proceed while the answers conflict
If the verified route cannot confirm the ACE66 message, the payment details differ or a material point remains unclear, stop. Urgency does not replace confirmation.
Deposit request warning signs
Match the request to a safe next action
| Message or request | Why it is suspicious | Safe next step |
|---|---|---|
| A new number claims to be ACE66 staff and immediately asks for a deposit | A display name and logo can be copied, while the sender has not been verified through a separate route. | Do not reply or pay. Open your previously verified route and ask about the exact request. |
| Pay now or your account, withdrawal or benefit will be blocked | Pressure reduces the time available to inspect the claim and recipient. | Let the stated deadline pass while you verify independently. Do not send a payment to avoid a threat. |
| Use a new personal account, temporary recipient or replacement QR code | An unexplained change can direct a payment to an unrelated person or mule account. | Stop and compare the details with current instructions displayed through the independently opened route. |
| Click this link to deposit, verify or contact support | A lookalike page can collect a login, banking details or identity documents. | Do not open it. Enter through your own bookmark or verified hostname and report the suspicious link. |
| Send a password, OTP, TAC, PIN, recovery code or screen-sharing approval | Those secrets can authorise access or transactions and are not identity-verification evidence. | Refuse, secure the affected account and financial accounts, and review any approval you did not initiate. |
| Make another deposit to unlock a withdrawal, bonus or frozen account | An extra payment demand can extend a scam and does not prove that the promised release exists. | Do not pay. Save the request, compare it with current published terms and contact verified support. |
Receiving account check
Check the recipient without treating one clean result as approval
Record the exact payment details
Write the bank name, recipient name, full account number or wallet identifier, requested amount, reference and time. Do not alter the ACE66 instruction while copying it.
Compare with the current verified screen
Open the ACE66 payment area yourself and compare each field. Similar names, matching colours or the same bank are not enough when the actual recipient differs.
Check the account or phone number in Semak Mule
Use PDRM's official Semak Mule portal before transferring to an unfamiliar Malaysian bank account or phone number. A reported match is a strong reason to stop and retain the result for a report.
Treat no Semak Mule record as inconclusive
No record does not mean PDRM has approved the recipient, and it does not verify an ACE66 relationship. A new or not-yet-reported account may still be risky.
Question an unexplained personal recipient
Do not assume a personal name is authorised because the sender calls the person an agent. Ask the independently reached ACE66 support route to confirm the exact destination and purpose.
Read the bank confirmation before approving
Check the actual recipient and amount inside your bank's own app. Cancel if the ACE66 details change, the name is unexpected or a warning appears.
Secrets that stay private
Never use a security secret to prove your identity to a message sender
Account and email passwords
Do not send an ACE66 password or the password for its recovery email. Change reused credentials from a clean, trusted route if either may be exposed.
OTP, TAC and verification codes
A code approves or confirms an action. Do not read it aloud, paste it into chat or enter it on a page reached from the suspected ACE66 fake staff message.
Bank PIN and full banking credentials
Use these only in your bank's official interface for an action you initiated. Verified ACE66 support does not need your bank login to examine a message report.
Push approvals and device prompts
Reject an unexpected sign-in, payment, device-registration or password-reset approval. A sender asking you to tap Approve is not proving an ACE66 role.
Recovery codes and security answers
Treat them like passwords. Do not photograph or forward them as part of an ACE66 support screenshot.
Screen sharing and remote-control access
Do not install an app or grant accessibility access so someone can 'help' with an ACE66 deposit. They may see codes, operate banking apps or capture documents.
Reach support safely
Open the 24-hour support route yourself, then start a new conversation
Close the sender's message
Do not use its link, phone number, QR code, contact card or forwarded support profile. Keeping the suspected ACE66 conversation open makes it easy to tap the wrong route.
Use an independently verified entry
Type the ACE66 hostname you previously checked or use a trusted bookmark. If you are unsure of the hostname, use the official-link verification Guide before entering credentials.
Find support inside the page or account
Use the 24-hour customer-service entry displayed in the ACE66 route you opened independently. Do not accept a replacement contact supplied by the person being checked.
Share a redacted report
Provide the sender identifier, time, wording, requested amount and masked recipient details. Remove ACE66 passwords, OTPs, full payment credentials, balances and unrelated personal data.
Ask for confirmation of the exact instruction
Request a clear answer about whether the payment purpose and recipient are current. Do not let a general statement about support turn into approval for different ACE66 details.
Report the impersonating profile
After saving evidence, use the messaging platform's report and block controls. Tell independently reached ACE66 support which profile was involved without asking other users to contact it.
Evidence without extra exposure
Save a short timeline that a bank, police officer or support agent can follow
Sender identity as displayed
Capture the number, username, profile link and display name used in the ACE66 impersonation. Note that a displayed identity may be false.
Complete request and pressure language
Save the messages that describe the ACE66 payment, deadline, threat, promised outcome and any instruction to keep the matter private.
Link, QR code and receiving details
Record the URL, final hostname if safely known, bank account, recipient name, wallet identifier and QR image. Do not reopen a suspicious link merely to improve the screenshot.
Transaction record
If money moved, save the amount, date, time, bank reference and receipt from the bank's official app. Mask unrelated balances before sharing the ACE66 incident file.
What you clicked, shared or installed
Write a factual sequence, including any OTP entered, approval accepted, document uploaded or remote tool installed. Accurate ACE66 incident scope matters more than embarrassment.
Protected storage
Keep the evidence where the suspected sender cannot access it. Do not store an ACE66 password, full card number or recovery secret in the same incident note.
If something already happened
Act according to the exposure you actually had
| What happened | Do this now | Who to contact |
|---|---|---|
| You received an ACE66 fake staff message but did not reply | Save the evidence, block and report the profile, then warn verified support through an independent route. | Independently reached support and the messaging platform. |
| You clicked a link but entered no details | Close the page, do not download anything, clear the risky session and check the device for unexpected downloads or permissions. | Cyber999 for a phishing or malicious-site incident, plus verified ACE66 support when relevant. |
| You shared an ACE66 password, OTP or approved a login | From a clean device, secure the recovery email first, change the exposed password, revoke unfamiliar sessions and reject unexpected approvals. | Verified support, the email provider, affected bank and Cyber999 according to the exposure. |
| You transferred money to the requested recipient | Call your bank's 24-hour scam hotline or NSRC 997 immediately. Do not wait for the ACE66 sender to answer or promise a refund. | Your bank, NSRC 997, then PDRM as soon as possible. 997 operates 24/7, including public holidays. |
| You installed an app or allowed remote control | Disconnect the device from networks, stop banking and ACE66 use on it, and secure affected accounts from a different trusted device. | Your bank, verified support, Cyber999 and PDRM if fraud or unauthorised access occurred. |
| You sent identity or payment documents | List exactly what was exposed, watch affected accounts and do not send more documents in response to a threat. | Verified support, the relevant bank or issuer, and PDRM or Cyber999 according to misuse observed. |
Two-minute decision
Use four timed checks before you continue
0:00 to 0:30: stop and save
Stop replying, clicking and paying. Capture the sender, exact ACE66 request, recipient, link and time without opening anything new.
0:30 to 1:00: open your own route
Leave the message. Open the ACE66 page or account through a hostname or bookmark you verified independently, then find its support entry.
1:00 to 1:30: compare the details
Check the stated purpose, amount and recipient against the current ACE66 screen. Use the official Semak Mule portal for an unfamiliar Malaysian account or phone number, remembering that no record is not approval.
1:30 to 2:00: stop or proceed
Proceed only when the independently reached route confirms the exact ACE66 instruction. If data or money was already sent, stop the verification exercise and begin the incident response immediately.
If money moved, call now
Contact your bank's scam hotline or NSRC 997 first, then lodge a PDRM report promptly. Do not let another ACE66 message delay the call.
If access or a device was exposed, contain it
Secure email, banking and ACE66 access from a clean device. Report phishing, credential compromise or malicious software to Cyber999 when applicable.
Fake staff and deposit scam FAQ
Answer the questions that usually delay a safe decision
Does an ACE66 logo, profile picture or display name prove that the sender is genuine?
No. Images and names can be copied, while caller ID or messaging accounts can be spoofed or compromised. Verify the exact request through a support route you opened independently, not through the sender's link, number or QR code.
If the sender knows my ACE66 username or activity, must they be staff?
No. A detail may come from prior messages, screenshots, reused information, guessing or a data exposure. Do not reveal more information to test the sender. Secure the account if the knowledge suggests that private data may be exposed.
Should I make another ACE66 deposit to unlock a withdrawal, benefit or account?
Do not act on an extra-payment request from an unverified sender. Save the request, compare it with current published terms and ask independently reached support about the exact purpose and recipient. A payment does not prove that a promised release will happen.
How do I use Semak Mule for an ACE66 payment request?
Open PDRM's official Semak Mule portal yourself and check the unfamiliar Malaysian bank account or phone number. Stop if it has a relevant report. If it has no record, continue the independent identity and recipient checks because a clean result is not approval or proof of safety.
What should I do if I already shared an ACE66 password or OTP?
Use a clean device to secure the linked email, change the exposed and reused passwords, revoke unfamiliar sessions and reject unexpected approvals. Contact affected banks through their own official channels and report a phishing or credential-compromise incident to Cyber999 when applicable.
What should I do after transferring money to a suspicious ACE66 recipient?
Call your bank's 24-hour scam hotline or NSRC 997 immediately, then lodge a PDRM report as soon as possible. Keep the transaction reference, recipient, amount, messages and timeline. NSRC 997 operates 24/7, but neither rapid reporting nor any other step guarantees recovery.

