Master @themasterrss

@ORamosBets Todo que sea superior a 0% en rojo es malo, en crypto lo sabemos bien

Day 2 of turning $25k into a $1M challenge

Red light therapy.

Mi suerte en la vida :)

I'll head to sleep now.. Hopefully the feds won't catch me 😱😱 Just kidding. They never will. New leaks that won the poll will be posted in the next 18 hours. Good night Fans, And Good night @RockstarGames 😉

Crypto holders right now:

Bull Theory @BullTheoryio

2 months ago

Bitcoin has surged +27% and $17,200 from $62,300 to $79,500 since Jim Cramer said he is selling all his BTC.

keyboard_arrow_left Previous keyboard_arrow_right Next

453 739 10K 936K 398

Se dice que han pillado al que estaba filtrando todos los clips de GTA VI Por lo visto era Noruego (aunque vivía en otro país)

😂😂😭😭 #GTA6 | #gtavıleak

Me siento orgulloso, hay que hacer más caso a PAPA, que se iba a 800 decían 👽😎, ya sabemos que va hacer tito Wash en Septiembre, GOOD DAY

We are so back 😄

Buenos días mi vida 🧡🧡

‼️ The GTA 6 leaks account is now polling followers on which stolen clip to drop next. Take-Two is DMCA-striking reuploads within minutes, Rockstar's own reveal lands August 27, and X has left the account up.

La acciones de Take Two se están desplomando, a los inversores no les gusta cuando una inversión de 2MM de dólares y el juego más esperado de la historia está en peligro :)

chapuzasinformatico @elchapuzas

2 months ago

Rockstar consigue contener la mayor filtración de GTA VI en años: gameplay real muestra seis estrellas, gasolina, moralidad, sigilo y almacenamiento de armas elchapuzasinformatico.com/2026/08/rockst…

8 5 50 13K 4

Wasted my prime years in crypto.

Trump becomes the first pro-Crypto president in history.

Thanks to you, the project will live on. Session now has a clear path forward. youtube.com/watch?v=rpMsr6…

Me gusta este porno

Ilya Miro @ilyamirox

6 months ago

Linux is just pornography at this point.

113 229 6K 501K 3K

Ese soy yo

naiive @naiivememe

6 months ago

People who've been in Crypto more than 5 years

35 74 664 36K 59

¡Esto es una locura! Investigadores encontraron una vulnerabilidad crítica en GitHub. Con un simple git push, un atacante podía inyectar datos en una cabecera interna de GitHub y acabar ejecutando código en sus servidores. Podía dar acceso a repos privados de otros usuarios y afectaba a GitHub Enterprise. GitHub lo arregló el mismo día pero ahí queda la historia.

‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP. The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years. Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box. The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root. Result: the next time anyone runs that program, it lets the attacker in as root. What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk. Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants. The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today. This vulnerability affects the following: 🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root 🔴 Kubernetes and container clusters: one compromised pod escapes to the host 🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner 🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root Timeline: 🔴 March 23, 2026: reported to the Linux kernel security team 🔴 April 1: patch committed to mainline (commit a664bf3d603d) 🔴 April 22: CVE assigned 🔴 April 29: public disclosure Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module: echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 2>/dev/null || true For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...

keyboard_arrow_left Previous keyboard_arrow_right Next