Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 24
  1. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Moving from blogger since google started flagging personal research blogs as "malware" and "malicious" content.

  2. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This was an accidental discovery, it took a total of 4 hours to find this.

  3. Regarding July 14th

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 (Un)fortunately I will be unable to mass disclose zerodays in July 14th, RoguePlanet took way more time than expected and truly drained me.

  4. Everything is up again

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 A huge thanks to churchofmalware for helping us to host our code !!!

  5. Regarding YellowKey PIN+TPM

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 A lot of you had the question of, how will YellowKey work with TPM+PIN.

  6. RoguePlanet, a quick history

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 In initial development, it was confirmed that this vulnerability was a remote code execution.

  7. It's patch Tuesday !!!

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Yes the rumors were true, a zero day vulnerability will be dropped this month as well https://github.com/MSNightmare/RoguePlanet Yes it's github again, Microsoft forgot that even if they banned my GitLab and…

  8. It's hard to keep going

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm starting to genuinely struggle with sleep and constant fevers.

  9. Announcing Bitskrieg

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Soooo, something extremely funny is happening.

  10. Articol fără titlu

  11. 7

  12. Welp

    Unsigned message because not important but tomorrow will be one of the hardest days in my life.

  13. July 14th

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Okay, So let me get this straight, when I actively asked you to communicate with me, you refused, humiliated me and made sure to insult me in front of people.

  14. Dear Microsoft,

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Regarding CVE-2026-45585, "Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey".

  15. MiniPlasma, a powerful LPE

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This one is accidental, I didn't even think cldflt.sys had that vulnerability.

  16. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Recently two researchers had interesting discoveries regarding YellowKey and GreenPlasma, The YellowKey is caused by the binary "autofstx.exe" which propagates all present volumes for transaction files, a re…

  17. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I just noticed that Microsoft silently patched the RedSun vulnerability, no CVE, no nothing, just a silent patch.

  18. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Here are the links, yes, two vulnerabilities this time.

  19. Remember this...

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 In the off chance, you decide that you want to proceed with whatever funny ideas you have in your head.

  20. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Here is the code, enjoy https://github.com/Nightmare-Eclipse/RedSun Now to address what some media articles wrote, first of all, I want to talk about MSRC official response regarding BlueHammer "Microsoft has

  21. Funny DOS tool

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 New tool as promised, this is a 0day (kinda), Microsoft will definitely try to mitigate this but it will be a lower priority.

  22. Public disclosure

    I was not bluffing Microsoft and I'm doing it again. https://github.com/Nightmare-Eclipse/BlueHammer Unlike previous times, I'm not explaining how this works, yall geniuses can figure it out.

  23. PGP Key

    -----BEGIN PGP PUBLIC KEY BLOCK----- mDMEacD4mxYJKwYBBAHaRw8BAQdA/+G2ISG5DwWQwITnrUwTrVkwk1XqJrHwuLiS mhT7rzC0EFRlcnJhaW4gUmVwdWJsaWOIlgQTFgoAPgIbAwULCQgHAgYVCgkICwIE FgIDAQIeAQIXgBYhBElO8B/8BZWEAoR5vsUWhEJLT9JsBQJpwPvqBQkLLaQYAAoJ EMUWhEJLT9JsBekA/R++4t7…

  24. I never wanted to reopen a blog and a new github account to drop code...