Un ataque de phishing detectado por Kaspersky Lab en enero de 2012 llevó esta técnica a otro nivel. Los ciberdelincuentes secuestraban cuentas legítimas y luego modificaban el nombre y la foto de perfil para hacerse pasar por "Facebook Security" o "El Equipo de Facebook". Desde estas cuentas comprometidas, enviaban mensajes de chat a todos los contactos de la víctima, advirtiendo que sus cuentas serían suspendidas a menos que reconfirmaran su información. El mensaje contenía un enlace a una página de phishing que no solo pedía el correo y la contraseña de Facebook, sino también la dirección de correo electrónico y la contraseña del webmail, la pregunta secreta e, incluso, los datos de la tarjeta de crédito. Este ataque fue particularmente insidioso porque se aprovechaba de la confianza que los usuarios tenían en sus propios amigos.
que recopilaban datos personales para empresas de telemarketing.
for similar browser exploits) to researchers who could find and report critical vulnerabilities. hackear facebook 2012
Before we dive into the hacking scandal, let's take a brief look at the state of Facebook in 2012. At the time, Facebook was just four years old, having launched in 2008. Despite its relatively short history, the platform had already become an integral part of online life, with users spending hours on the site every day. In 2012, Facebook was still in the process of expanding its features and services, including the introduction of Timeline, a new profile layout that allowed users to curate their Facebook history.
En 2012, internet estaba lleno de páginas web y videos de YouTube que prometían hackear cualquier cuenta de Facebook introduciendo únicamente el enlace del perfil de la víctima. Estos sitios web mostraban barras de carga falsas y líneas de código en pantalla para simular un proceso informático avanzado. La realidad de las descargas: Malware y Troyanos
According to reports, the hackers used a technique called "spear phishing" to gain access to the Facebook accounts. Spear phishing involves sending targeted emails to specific individuals, often with malicious links or attachments that, when clicked, install malware on the victim's device. In this case, the hackers sent emails to Facebook employees, tricking them into revealing their login credentials. Un ataque de phishing detectado por Kaspersky Lab
: It forced platforms like Facebook to implement more robust security, such as Two-Factor Authentication (2FA)
Learn about the 2012 Facebook hacking scandal, including the methods used by hackers, the impact on users, and Facebook's response. Discover how the incident shaped the social media industry's approach to security.
Un ataque de phishing detectado por Kaspersky Lab en enero de 2012 llevó esta técnica a otro nivel. Los ciberdelincuentes secuestraban cuentas legítimas y luego modificaban el nombre y la foto de perfil para hacerse pasar por "Facebook Security" o "El Equipo de Facebook". Desde estas cuentas comprometidas, enviaban mensajes de chat a todos los contactos de la víctima, advirtiendo que sus cuentas serían suspendidas a menos que reconfirmaran su información. El mensaje contenía un enlace a una página de phishing que no solo pedía el correo y la contraseña de Facebook, sino también la dirección de correo electrónico y la contraseña del webmail, la pregunta secreta e, incluso, los datos de la tarjeta de crédito. Este ataque fue particularmente insidioso porque se aprovechaba de la confianza que los usuarios tenían en sus propios amigos.
que recopilaban datos personales para empresas de telemarketing.
for similar browser exploits) to researchers who could find and report critical vulnerabilities.
Before we dive into the hacking scandal, let's take a brief look at the state of Facebook in 2012. At the time, Facebook was just four years old, having launched in 2008. Despite its relatively short history, the platform had already become an integral part of online life, with users spending hours on the site every day. In 2012, Facebook was still in the process of expanding its features and services, including the introduction of Timeline, a new profile layout that allowed users to curate their Facebook history.
En 2012, internet estaba lleno de páginas web y videos de YouTube que prometían hackear cualquier cuenta de Facebook introduciendo únicamente el enlace del perfil de la víctima. Estos sitios web mostraban barras de carga falsas y líneas de código en pantalla para simular un proceso informático avanzado. La realidad de las descargas: Malware y Troyanos
According to reports, the hackers used a technique called "spear phishing" to gain access to the Facebook accounts. Spear phishing involves sending targeted emails to specific individuals, often with malicious links or attachments that, when clicked, install malware on the victim's device. In this case, the hackers sent emails to Facebook employees, tricking them into revealing their login credentials.
: It forced platforms like Facebook to implement more robust security, such as Two-Factor Authentication (2FA)
Learn about the 2012 Facebook hacking scandal, including the methods used by hackers, the impact on users, and Facebook's response. Discover how the incident shaped the social media industry's approach to security.
108 ms
logon.aspx
128 ms
segoeui-regular.ttf
214 ms
owa.tragsa.es accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
owa.tragsa.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
owa.tragsa.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Owa.tragsa.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Owa.tragsa.es main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
owa.tragsa.es
Open Graph description is not detected on the main page of Owa Tragsa. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: