![\"Illustrative](\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/10\/knab-qr-code-scam-fake-bank-security-check-illustration.png\" "\\"\\"")
<\/figure>\nOverview<\/h2>\nA security check that can authorize somebody else’s login<\/h3>\n
The Knab QR code scam combines bank impersonation with a misleading login page. A supposed employee tells you to scan a code to protect your account.<\/p>\n
The dangerous part is the approval inside your real banking app. You may think you’re confirming a safety check while actually allowing another person to sign in.<\/p>\n
This is not a claim that Knab’s normal QR login is fraudulent. Criminals are misusing a legitimate feature and disguising whose login you’re approving.<\/p>\n
The warning comes from the bank itself<\/h3>\n
Knab’s bank-helpdesk fraud warning<\/a> describes callers who direct customers to websites and ask them to scan QR codes.<\/p>\n Its explanation identifies the key deception: the code can belong to a login the fraudster started on the genuine banking website.<\/p>\n The caller supplies a different story about what that action means. A familiar logo, convincing voice, or recognizable telephone number doesn’t make that story true.<\/p>\n The page pictured here is a generated illustration with a fictional address and a QR-like placeholder. It demonstrates the pretext, not a captured criminal website.<\/p>\n If somebody else arranged the page and is coaching the approval, stop. Restart the conversation through the Knab app or another contact route you already trust.<\/p>\n People often expect fraud to involve an obviously fake app. Here, the banking application on your phone can be entirely genuine.<\/p>\n The misunderstanding happens between two screens. One screen tells you that you’re completing security maintenance; the other requests permission for a particular account action.<\/p>\n A QR code carries information. It doesn’t independently establish that the person who displayed it is a bank employee or that their explanation is accurate.<\/p>\n Think about who started the login. When you visit your bank independently, you know why you need access. During an unexpected call, somebody else controls that context.<\/p>\n The caller may describe a routine approval as cancellation, verification, or protection. Those words don’t change what the banking system processes.<\/p>\n This is why reading the app matters more than listening to the explanation over the phone. An instruction to approve a login isn’t the same as cancelling fraud.<\/p>\n You also don’t need to prove your innocence by cooperating. Being cautious with an unexpected instruction is sensible, even if the caller becomes impatient.<\/p>\n The approach starts with a problem that sounds expensive to ignore: suspicious activity, an unfamiliar device, or money that supposedly needs protecting.<\/p>\n Knab warns that criminals can already possess personal information. Knowing your name or other details can make the conversation feel less like a random cold call.<\/p>\n That familiarity isn’t an employee check. Information can come from earlier phishing, exposed records, public sources, or things you disclose while answering questions.<\/p>\n The caller may also manipulate the displayed telephone number. Seeing a bank’s number on your screen doesn’t establish who is speaking.<\/p>\n The practical test comes next. A genuine concern can be checked independently; a fraudster needs you to remain inside their instructions.<\/p>\n You are told to open a website for verification. Its wording may describe an updated banking environment or a procedure for undoing suspicious activity.<\/p>\n A copied logo makes the page recognizable. It does not make the address belong to Knab, and the caller’s assurance cannot fix an unrelated domain.<\/p>\n Some addresses place a bank name inside a longer string. Read the actual domain, not just the familiar letters at its beginning.<\/p>\n Knab identifies its personal banking address as persoonlijk.knab.nl. For a real login, type that address yourself instead of following a caller’s supplied route.<\/p>\n Don’t use a search advertisement as a substitute for that check. The first result can still be an unsuitable destination for an urgent banking conversation.<\/p>\n The fraudster can begin a login through the genuine service and put the resulting QR code into the misleading page you are viewing.<\/p>\n You scan it believing that the task concerns your own security. The bank’s app then asks you to confirm the associated action.<\/p>\n The code’s appearance isn’t the decisive warning. Even a functional code can serve the wrong person’s request when its purpose has been misrepresented.<\/p>\n At this point, put the phone conversation aside and read the request literally. Does it ask you to sign in or authorize access?<\/p>\n If you didn’t initiate that login independently, decline it. You do not need to finish a suspicious procedure to find out whether the caller is trustworthy.<\/p>\n Confirming the login may let the criminal enter your online banking environment. The approval can be genuine even though your reason for giving it was deceptive.<\/p>\n A confirmed login and an approved transfer are different actions. Tell the bank about each prompt you accepted, even if no money has moved yet.<\/p>\n The caller may continue asking for additional approvals or actions. What they call a reversal could instead be another request requiring your permission.<\/p>\n Stop when an unfamiliar login or transaction appears. A person who says they are cancelling fraud should not need you to approve unexplained account activity.<\/p>\n If you already approved the login, tell Knab immediately. Waiting for a missing balance wastes time when unauthorized access may already exist.<\/p>\n Knab also warns about supposed safe accounts, requests for security codes, and instructions to install software that lets another person view or control a device.<\/p>\n If the call moves on to transfers or software, stop there too. When contacting Knab, explain those instructions alongside the QR approval.<\/p>\n Moving savings to a new destination does not become protective simply because the caller describes it that way. Verify the recipient and purpose outside the conversation.<\/p>\n A remote-support application can be legitimate software with a dangerous permission granted to the wrong person. Its presence in an app store doesn’t validate the caller.<\/p>\n Once the instructions reach your banking permissions, security codes, or computer controls, the conversation has moved far beyond a harmless account notification.<\/p>\n A case reference, professional greeting, or detailed account story can sound reassuring. None of those details independently proves that the speaker works for Knab.<\/p>\n Don’t let the caller choose how you verify their identity. End the call and start a fresh contact through your established banking application.<\/p>\n If they object that hanging up will interrupt an investigation, treat that pressure as another reason to leave. You can explain the concern to the real bank.<\/p>\n A browser’s secure-connection symbol concerns the connection to a website. It isn’t a certificate that the page’s instructions are honest.<\/p>\n A fraudulent site can have an encrypted connection. The relevant questions remain who controls the address and what action the page wants you to authorize.<\/p>\n For the same reason, a clean-looking screen isn’t enough. Focus on the address and the approval request rather than how closely the colors resemble your bank.<\/p>\n Read the wording before confirming. If an approval names a login, a device, or a payment, evaluate that action directly.<\/p>\n Don’t substitute the caller’s explanation for the message on screen. Ask yourself whether you would approve the same request without the caller’s story.<\/p>\n When the answer is no, decline it. You can investigate safely after leaving the staged security check.<\/p>\n Fraud calls can move quickly. You may remember scanning something but feel uncertain about the buttons you pressed or the order in which screens appeared.<\/p>\n Don’t postpone contacting the bank while trying to reconstruct a perfect account. Start with what you know and clearly identify what you cannot remember.<\/p>\n For example, distinguish seeing a QR code, scanning it, opening the app, and confirming a request. Those are separate events, even when they happened within seconds.<\/p>\n Tell the bank whether the caller watched through screen sharing or only spoke over the phone. That changes what the other person may have observed.<\/p>\n Describe the wording you remember from the approval screen. If you saved a screenshot, provide it through the bank’s own secure reporting process.<\/p>\n If you didn’t take a screenshot, don’t reopen the suspicious page or repeat the scan to reproduce it. You could create another exposure while collecting evidence.<\/p>\n Also mention any confirmation that arrived after the call ended. A later notification can help establish what was processed, even if you no longer trust the caller’s explanation.<\/p>\n Keep your own actions and the caller’s claims in separate sentences. You might know you approved a login while only being told that money was protected.<\/p>\n Finally, identify which device you used for the page and which held the banking app. Don’t assume the bank will infer that arrangement from the phrase QR scam.<\/p>\n A clear, imperfect timeline is more useful than a confident guess. Let the genuine fraud team assess account records while you explain the parts you actually witnessed.<\/p>\n Stop the guided session.<\/strong> End the telephone conversation, close the supplied page, and decline outstanding approvals. Don’t ask the same caller to undo the situation.<\/p>\n If they call again, you do not owe them another explanation. Keep the next contact separate from the channel that delivered the suspicious instruction.<\/p>\n<\/li>\n Tell Knab exactly what you approved.<\/strong> Use the bank’s app or independently obtained official contact information. Report a scanned QR code and confirmed login explicitly.<\/p>\n Knab’s official warning lists its fraud alarm line as 020 303 1659. Check the number on its own website before using it.<\/p>\n<\/li>\n Ask the bank to address active access.<\/strong> Explain whether you shared credentials, approved a device, or saw a successful login. A password change alone may not address everything.<\/p>\n Ask which sessions, permissions, account settings, and payment restrictions need reviewing. Follow instructions from the independently contacted bank, not the previous caller.<\/p>\n<\/li>\n Identify any money movements.<\/strong> Check recent transfers and pending activity with Knab. Give the amount, time, destination, and explanation the caller used.<\/p>\n Request an urgent fraud assessment and ask whether stopping or recalling a payment is possible. Recovery depends on the circumstances; no outside caller can guarantee it.<\/p>\n<\/li>\n Deal separately with remote-control access.<\/strong> If you installed software or shared your screen, stop the connection and avoid banking on that device until it is assessed.<\/p>\n A Malwarebytes<\/a> scan can help investigate malicious downloads. It cannot revoke a banking session or retrieve money transferred during the call.<\/p>\n<\/li>\n Save a useful record.<\/strong> Keep the messages, page address, approximate call time, requested actions, and transaction references. Never preserve passwords inside your notes.<\/p>\n Write down what you remember while it is fresh. Separate actions you completed from instructions you refused, so the bank can prioritize the remaining risks.<\/p>\n<\/li>\nThe checks that matter before you touch the code<\/h3>\n
\n
Why a Genuine Banking App Can Still Appear in the Scam<\/h2>\n
How the Knab QR Code Scam Works<\/h2>\n
Step 1: An urgent bank call interrupts your day<\/h3>\n
Step 2: The caller sends you to a convincing-looking page<\/h3>\n
Step 3: A real login request is presented as a safety measure<\/h3>\n
Step 4: Approval can give the fraudster access<\/h3>\n
Step 5: The story can expand into money transfers or remote access<\/h3>\n
Check the Request, Not the Performance<\/h2>\n
A confident voice doesn’t establish employment<\/h3>\n
A padlock doesn’t approve the page’s purpose<\/h3>\n
Your own app is where the action becomes clear<\/h3>\n
What to Tell Knab When You Can’t Remember Every Tap<\/h2>\n
What to Do if You Have Fallen Victim to This Scam<\/h2>\n
\n