Passkey-themed scams show why Bangladesh teams should verify the request
A CIRT advisory describes attackers using authentication changes as a pretext. It does not identify the passkey itself as the vulnerability.

An authentication request can be fraudulent even when it uses familiar security language. A BGD e-GOV CIRT advisory published on 14 September describes attackers impersonating helpdesk staff and using passkey or multifactor-authentication changes as a pretext to compromise cloud identities.
The advisory distinguishes the social-engineering approach from a flaw in passkeys themselves. It describes victims being directed to attacker-controlled pages or persuaded to complete authentication processes that benefit the attacker.
This article revisits that advisory as a workplace process issue for Bangladesh organisations. It does not report a new campaign discovery today or establish that any particular employer has been targeted.
Evidence: Official release, 2026-09-14.
Entivel analysis: make legitimate support recognisable
A business can reduce ambiguity by giving staff a clear way to check whether an unexpected request is genuine. That process should use an established internal route rather than contact details supplied in the unexpected message itself.
For a Dhaka employer with staff working across locations, the practical question is whether someone can pause an urgent request and obtain an independent confirmation without losing access to necessary work. A policy that exists only in a long document may be difficult to use in the middle of a persuasive phone call.
Include identity changes in the operating record
When an authentication method is added or changed, the organisation needs a way to connect the event with an authorised request. The relevant records and review responsibilities depend on the systems in use and should be defined by the organisation's administrators.
The same principle applies when an employee changes roles or leaves. A clear handover between workforce administration and technical administration helps identify which access decisions require attention. It does not remove the need for appropriate technical controls or a proper investigation if suspicious activity occurs.
The advisory also shows why the absence of an obvious malicious attachment is not enough to settle a security question. A business should examine the context of the request and the access being authorised, rather than relying only on the appearance of a message or the familiarity of its vocabulary.
Useful training can therefore focus on a recognisable decision: how to verify a request before approving a security change. That is more actionable than asking every employee to diagnose an entire attack campaign.
From Entivel
Organisations reviewing these responsibilities can explore Entivel's cybersecurity engineering services and contact the team. These are Entivel offerings, distinct from the advisory's findings.
Questions about this story? Request a correction or send feedback.