Farmácia do Lourel: From Email Fraud to Account Protection
- Published:
- Reading time:
- 4 min read
Farmácia do Lourel contacted Studio 17 after reporting that its company email accounts had been compromised and used to send fraudulent payment links to clients. Some clients said they had already paid. Studio 17 investigated the available evidence, protected the email accounts the pharmacy asked it to address and developed procedures, documentation and training materials.
Responding to Fraudulent Emails and Payment Requests
Farmácia do Lourel came to Studio 17 with an urgent concern: the pharmacy reported that someone had gained access to its company email accounts and was sending clients fake emails containing fraudulent payment links. Some clients had already contacted the pharmacy to say they had paid.
01The challenge: respond to reported email fraud
The immediate concern was the reported misuse of company email and the payment requests reaching clients. Understanding how access might have been gained was part of the response, alongside protecting the accounts and giving the pharmacy practical next steps.
Studio 17 investigated the available account evidence and protected all the email accounts the pharmacy asked it to address. The work then expanded into documentation, procedures and training materials to help staff recognise suspicious requests and respond consistently.
02Investigate access and protect the requested accounts
With authorised visual access, the review considered available security activity, sessions, recognised devices, authentication and recovery arrangements, email settings and connected applications. A sample of sent correspondence and the inspected browser profile were also reviewed.
The review distinguished the pharmacy’s report of fraudulent emails and clients’ reported payments from what could be established through the available account evidence. Studio 17 investigated possible access routes without claiming to have identified the original entry point.
03Build procedures people can use
Studio 17 prepared an internal security policy and a daily working manual. These connected account ownership, access permissions, confidential information and device use to familiar tasks: checking a recipient and attachment, locking an unattended workstation and reviewing access when someone leaves.
An incident procedure set out the immediate response sequence and separated employee responsibilities from management and technical-support decisions. Escalation contacts and an incident record gave the team a structure for recording what happened, what was observed and what action followed.
A separate phishing and payment-verification procedure addressed suspicious instructions, including changes to bank details within an existing email conversation. It called for independent confirmation through a known contact and separate approval for sensitive payment changes.
| Prepared material | Decision it supports | Practical component |
|---|---|---|
| Policy and daily manual | How routine account and device use should be handled | Defined responsibilities and everyday checks |
| Incident procedure | Who acts when something appears wrong | Response sequence, escalation contacts and incident record |
| Payment-verification procedure | How sensitive payment changes should be checked | Independent confirmation and approval record |
| Protection and verification plan | How follow-up work should be tracked | Account/device checklists and an execution matrix |
04Prepare training around real decisions
The training package included a 28-slide presentation designed for approximately 60 minutes, with speaker notes, discussion prompts and clearly fictional examples related to pharmacy work. Exercises were designed around suspicious messages, unexpected authentication requests, payment confirmation and incident reporting.
Three Google Forms assessments covered daily security, phishing/payments/incidents, and management coordination. A trainer guide supplied answer keys, scoring criteria and a practical exercise. Assessment grades were configured for release after manual review, with correct answers and other participants’ response summaries hidden.
05The documented outcome
The response combined investigation and protection of the requested email accounts with review findings, procedures, working records and training materials. The documentation supported the technical work: it made responsibilities and follow-up steps explicit and defined how to record an action and its verification before marking it complete.
A useful security procedure states who acts, what they do and how the result is recorded.
06What the evidence does—and does not—show
Farmácia do Lourel reported compromised email accounts and fraudulent payment requests. Studio 17 protected every email account the pharmacy asked it to address. The review did not establish the original access route or a complete history of account changes. Training materials were prepared; attendance and measured changes in employee performance were not established.
07A practical takeaway for business teams
The useful connection is between a review and the work people need to carry out afterwards: clear responsibilities, usable instructions and a record of follow-up. Businesses considering digital systems and workflow support can start by describing the process, the people involved and the decisions that need to be clearer.
Studio 17 can help discuss an operational support brief around those requirements.
A useful security procedure states who acts, what they do and how the result is recorded.
Hugo Filipe
Clarify how your team should respond
Tell us which processes need clearer rules and who staff turn to when a problem arises. We can discuss the procedures, working records and guidance your business needs.