Digital First Aid Kit/topics/suspicious-messages.md — Spanish @ L10N.SPACE: Please contact the organizations below who can support you. Afterward, …

Key

English

Spanish

Actions

> Sharing your suspicious message can help protect your colleagues and community who may also be affected. You may also like to reach for help to someone you trust to advise you if the message is dangerous. Consider sharing the message with organizations that can analyze them.
>
> To share your suspicious message, make sure to include the message itself as well as information about the sender. If the message was an email, please make sure to include the full email including headers using the [following guide by the Computer Incident Response Center Luxembourg (CIRCL)](https://www.circl.lu/pub/tr-07/).

* Sense of urgency: suspicious emails typically warn of a sudden change to an account and ask you to act immediately to verify your account.
* In the body of an email, you might see questions asking you to “verify” or “update your account” or “failure to update your records will result in account suspension”. It is usually safe to assume that no credible organization to which you have provided your information will ever ask you to re-enter it, so do not fall for this trap.
* Beware of unsolicited messages, attachments, links and login pages.
* Watch out for spelling and grammar errors.
* Click to view the full sender address, not only the displayed name.
* Be mindful of shortened links - they can hide a malicious link behind it.
* When you hover your mouse over a link, the actual URL you are being directed to is displayed in a popup or at the bottom of your browser window.
* Email headers including the "from:" value could be carefully crafted to look like they are legitimate. By examining the SPF and DKIM headers, you can tell respectively if an IP address is (or is not) allowed to send emails on behalf of the sender's domain, and if the headers or the content have been changed in transit. In a legitimate email, the [SPF](https://dmarcly.com/blog/how-to-implement-dmarc-dkim-spf-to-stop-email-spoofing-phishing-the-definitive-guide#what-is-spf) and [DKIM](https://dmarcly.com/blog/how-to-implement-dmarc-dkim-spf-to-stop-email-spoofing-phishing-the-definitive-guide#what-is-dkim) values should always be 'PASS', otherwise an email should not be trusted. The reason is that the email is spoofed or, in rare cases, the mail server is not configured correctly.
* [Digital signatures](https://www.gnupg.org/gph/en/manual/x135.html) can tell us if an email has been sent by the legitimate sender and if it has been modified or not along the way. If the email is signed, check if the signature is verified or not. In order to verify a signature, you will need OpenPGP as well as the public key associated with the ID in the signature of the message. Most of the modern email clients that support digital signatures will automate the verification for you and tell you through their user interface if a signature is verified or not.
* A compromised account could issue a malicious email or message that could verify all the conditions above and look legitimate. However, usually the content of the message will be unusual. If the content of the email message seems strange, it's always a good idea to check with the legitimate sender through a different channel of communication before taking any action.
* It is always a good practice to read and write your emails in plain text. HTML-based emails could be rendered in a way that hides malicious code or URLs. You can find instructions on how to disable HTML in different email clients in [this post](https://www.maketecheasier.com/read-email-in-plain-text/ )
* Use the latest version of the operating system on your phone or computer (check version for [Android](https://en.wikipedia.org/wiki/Android_version_history), [iOS](https://en.wikipedia.org/wiki/IOS_version_history), [macOS](https://en.wikipedia.org/wiki/MacOS_version_history) and [Windows](https://en.wikipedia.org/wiki/Microsoft_Windows)).
* Update as soon as possible your operating system and all the apps/programs you have installed especially those which receive information (browsers, messaging and chatting apps/programs, email clients, etc.). Remove all apps/programs you do not need.
* Use a reliable browser (e.g. Mozilla Firefox). Increase your browser security by reviewing the extensions/add-ons installed in your browser. Leave only those you trust (for example: HTTPS Everywhere, Privacy Badger, uBlock Origin, Facebook Container, Cookie AutoDelete, NoScript).
* Make regular secure backups of your information.
* Protect your accounts with strong passwords, 2-factor authentication and secure settings.

Key

English

Spanish

Actions

English	Spanish
No related strings found in the glossary.

English

Spanish

No related strings found in the glossary.

Key	English	Spanish
	> Sharing your suspicious message can help protect your colleagues and community who may also be affected. You may also like to reach for help to someone you trust to advise you if the message is dangerous. Consider sharing the message with organizations that can analyze them. > > To share your suspicious message, make sure to include the message itself as well as information about the sender. If the message was an email, please make sure to include the full email including headers using the [following guide by the Computer Incident Response Center Luxembourg (CIRCL)](https://www.circl.lu/pub/tr-07/).
	Do you need further help?
	- [Yes, I need more help](#help_end) - [No, I've solved my problem](#resolved_end)
	### device-security_end
	> In case some files were downloaded to your device, your device may be at risk!
:142	Please contact the organizations below who can support you. Afterward, please [share your suspicious message](#share).
	:[](organisations?services=device_security)
	### account-security_end
	> In case you entered your credentials, or you were the victim of a cross-site script attack, your accounts may be at risk! > > If you think your account is compromised, it is recommended you also follow the Digital First Aid Kit workflow on [compromised accounts](../../../account-access-issues). > > It is suggested that you also inform your community about this phishing campaign, and share the suspicious message with organizations that can analyze them.
	Would you like to share information on the message you received or do you need further assistance before?
	- [I want to share the suspicious message](#share) - [I need more help to secure my account](#account_end) - [I need more help to analyze the message](#analysis_end)
	### suspicious-device_end
	> If you clicked on a link and aren't sure what happened, your device may have been infected without you noticing. If you want to explore this possibility, or have the feeling your device may be infected go to the workflow ["My device is acting suspiciously"](../../../device-acting-suspiciously).
	### help_end
	> You should seek help from your colleagues or others to better understand risks from the information you shared. Other people in your organisation or network may also have received similar requests.
:169	Please contact the organizations below who can support you. Afterward, please [share your suspicious message](#share).	### account_end
	:[](organisations?services=digital_support)	Si tu cuenta ha sido comprometida y necesitas ayuda para protegerla, comunicate con las organizaciones a continuación descritas que pueden ayudarte.
	### account_end
	If your account has been compromised and you need help to secure it, please contact the organizations below who can support you.	### analysis_end
	:[](organisations?services=account)	Las siguientes organizaciones pueden recibir tu mensaje sospechoso e investigar a fondo en tu nombre:
	### analysis_end
	The following organizations can receive your suspicious message and investigate it further for you:
	:[](organisations?services=forensic&services=vulnerabilities_malware)
	### resolved_end
	Hopefully this DFAK guide was useful. Please give feedback [via email](mailto:[email protected]).
	### final_tips	La primera regla a recordar: nunca divulgues información personal en correos electrónicos. Ninguna institución, banco u otras organizaciones solicitarán esta información por correo electrónico. Puede que no siempre sea fácil saber si un correo electrónico o sitio web es legítimo, pero hay algunos consejos que pueden ayudarte a evaluar lo que recibiste.
	The first rule to remember: Never give out any personal information in emails. No institution, bank or otherwise will ever ask for this information via email. It may not always be easy to tell whether an email or website is legitimate, but there are some tips that can help you assess the email you have received.
	* Sense of urgency: suspicious emails typically warn of a sudden change to an account and ask you to act immediately to verify your account. * In the body of an email, you might see questions asking you to “verify” or “update your account” or “failure to update your records will result in account suspension”. It is usually safe to assume that no credible organization to which you have provided your information will ever ask you to re-enter it, so do not fall for this trap. * Beware of unsolicited messages, attachments, links and login pages. * Watch out for spelling and grammar errors. * Click to view the full sender address, not only the displayed name. * Be mindful of shortened links - they can hide a malicious link behind it. * When you hover your mouse over a link, the actual URL you are being directed to is displayed in a popup or at the bottom of your browser window. * Email headers including the "from:" value could be carefully crafted to look like they are legitimate. By examining the SPF and DKIM headers, you can tell respectively if an IP address is (or is not) allowed to send emails on behalf of the sender's domain, and if the headers or the content have been changed in transit. In a legitimate email, the [SPF](https://dmarcly.com/blog/how-to-implement-dmarc-dkim-spf-to-stop-email-spoofing-phishing-the-definitive-guide#what-is-spf) and [DKIM](https://dmarcly.com/blog/how-to-implement-dmarc-dkim-spf-to-stop-email-spoofing-phishing-the-definitive-guide#what-is-dkim) values should always be 'PASS', otherwise an email should not be trusted. The reason is that the email is spoofed or, in rare cases, the mail server is not configured correctly. * [Digital signatures](https://www.gnupg.org/gph/en/manual/x135.html) can tell us if an email has been sent by the legitimate sender and if it has been modified or not along the way. If the email is signed, check if the signature is verified or not. In order to verify a signature, you will need OpenPGP as well as the public key associated with the ID in the signature of the message. Most of the modern email clients that support digital signatures will automate the verification for you and tell you through their user interface if a signature is verified or not. * A compromised account could issue a malicious email or message that could verify all the conditions above and look legitimate. However, usually the content of the message will be unusual. If the content of the email message seems strange, it's always a good idea to check with the legitimate sender through a different channel of communication before taking any action. * It is always a good practice to read and write your emails in plain text. HTML-based emails could be rendered in a way that hides malicious code or URLs. You can find instructions on how to disable HTML in different email clients in [this post](https://www.maketecheasier.com/read-email-in-plain-text/ ) * Use the latest version of the operating system on your phone or computer (check version for [Android](https://en.wikipedia.org/wiki/Android_version_history), [iOS](https://en.wikipedia.org/wiki/IOS_version_history), [macOS](https://en.wikipedia.org/wiki/MacOS_version_history) and [Windows](https://en.wikipedia.org/wiki/Microsoft_Windows)). * Update as soon as possible your operating system and all the apps/programs you have installed especially those which receive information (browsers, messaging and chatting apps/programs, email clients, etc.). Remove all apps/programs you do not need. * Use a reliable browser (e.g. Mozilla Firefox). Increase your browser security by reviewing the extensions/add-ons installed in your browser. Leave only those you trust (for example: HTTPS Everywhere, Privacy Badger, uBlock Origin, Facebook Container, Cookie AutoDelete, NoScript). * Make regular secure backups of your information. * Protect your accounts with strong passwords, 2-factor authentication and secure settings.
	#### Resources	Aquí van una serie de recursos para detectar mensajes sospechosos y evitar ser engañados.
	Here are a number of resources to spot suspicious messages and avoid being phished.
	* [Citizen Lab: Communities at risk - Targeted Digital Threats Against Civil Society](https://targetedthreats.net) * [Surveillance Self-Defense: How to Avoid Phishing Attacks](https://ssd.eff.org/en/module/how-avoid-phishing-attacks) * [Security Without Borders: Guide to Phishing](https://guides.securitywithoutborders.org/guide-to-phishing/)

Key	English	Spanish
	:[](organisations?services=digital_support)	Si tu cuenta ha sido comprometida y necesitas ayuda para protegerla, comunicate con las organizaciones a continuación descritas que pueden ayudarte.
	Keep in mind that receiving a suspicious email does not necessarily mean that your account has been compromised. If you think an email or message is suspicious, don't open it. Don't reply to the email, don't click any links, and don't download any attachments.	Ten en cuenta que recibir un correo electrónico sospechoso no significa necesariamente que tu cuenta haya sido comprometida. Si crees que un correo electrónico o un mensaje es sospechoso, no lo abras. No respondas al correo electrónico, no hagas clic en ningún enlace y no descargues ningún archivo adjunto.
	### known-sender	### known-sender
	- [Yes](#resolved_end) - [No](#share)	- [Sí](#resolved_end) - [No](#share)
	> The fact that you clicked on a suspicious link and you didn't notice any strange behaviour doesn't meant that no malicious action took place in the background. There are some scenarios that you should think about. The least concerning is that the message you received was spam used for advertising purposes. In this case some ads will pop up. In some cases these ads could be malicious too.
	### cross-site-script
	### cross-site-script-admin-compromised
	:[](organisations?services=forensic)
	### cross-site-script_end
	- [I want to assess if my device got infected](../../../device-acting-suspiciously) - [I think I'm fine](#final_tips)
	> Depending on the type of information you shared, you may need to take immediate action.
	### account_end
	If you are not certain about the authenticity of the message you received, or what to do about it, you can use the following questionnaire as a guiding tool to further diagnose the situation or to share the message with external trusted organizations that will provide you with a more detailed analysis of your message.	Si no estás seguro de la autenticidad del mensaje que recibes, o qué hacer al respecto, puedes usar el siguiente cuestionario como herramienta para diagnosticar la situación o compartir el mensaje con organizaciones externas de confianza que te proporcionarán un análisis más detallado del mensaje.
	> In case you entered your credentials, or you were the victim of a cross-site script attack, your accounts may be at risk! > > If you think your account is compromised, it is recommended you also follow the Digital First Aid Kit workflow on [compromised accounts](../../../account-access-issues). > > It is suggested that you also inform your community about this phishing campaign, and share the suspicious message with organizations that can analyze them.
:142	Please contact the organizations below who can support you. Afterward, please [share your suspicious message](#share).
:169	Please contact the organizations below who can support you. Afterward, please [share your suspicious message](#share).	### account_end

Digital First Aid Kit

topics/suspicious-messages.md

Spanish

Translate

Translation

Things to check

Mismatched full stop

Reused translation

Glossary

String information

Key

Source string location

String age

Last updated

Source string age

Translation file