Skip navigation
android persistent threat
0:00 / 0:35

android persistent threat

ellie🌸

@ptrpaws3.8K followers

Visit on X
1,447 likesDownloadOriginal post

155,949 views

android persistent threat

40 Comments

Comments from the original post on X (Twitter)

  • ellie🌸's profile picture

    @ptrpaws

    don't worry about it kitten

    95 likes

  • Tarek's profile picture

    @Tarek724375

    Did you have to add that shitty dubstep music?

    52 likes

  • ellie🌸's profile picture

    @ptrpaws

    yes

    42 likes

  • zauce🍇💫's profile picture

    @kebabenseLSS

    Is this just dirty flag running on boot?

    17 likes

  • ellie🌸's profile picture

    @ptrpaws

    no. every bug involved was found by me

    36 likes

  • Gashbin Ayoob Othman's profile picture

    @GashbinO68368

    Using AI to find this vulnerability doesn't mean you discovered anything special or did it yourself. Anyone could do what you've done if they had the money or access to this model.

    14 likes

  • ellie🌸's profile picture

    @ptrpaws

    what

    164 likes

  • Gashbin Ayoob Othman's profile picture

    @GashbinO68368

    Did you use AI or not?

    2 likes

  • Fred's profile picture

    @fred6279

    Does this fail on Graphene?

    11 likes

  • ellie🌸's profile picture

    @ptrpaws

    yes. graphene has appropriate mitigations that prevents exploitation

    127 likes

  • laura🏳️‍⚧️Ⓐ☭🇵🇸's profile picture

    @laurameow161

    show if your bootloader is locked with factory keys

    10 likes

  • Denay 🇮🇹's profile picture

    @denay39th

    using pixel without graphene is crime towards humanity

    5 likes

  • kekw 's profile picture

    @_m0ab

    so what are the chances of a root releasing that doesn't fuck with Google play api

    4 likes

  • dialga's profile picture

    @dialga1453

    is this more convenient for modules than the dirtyfrag method??? i assume the bootloader is locked tho

    3 likes

  • Pavit Chhabra's profile picture

    @mesosan16

    sus. CVE please?

    3 likes

  • Geneviève Philippe's profile picture

    @GenevivePhiPhi

    Up to date but it's Android 15 It's because you need a specific range of stock models and/or a specific range of stock kernels that have the exploitable CVE's

    2 likes

  • Certified Winner™'s profile picture

    @fedcoiner

    You're a man nigga, admit it

    2 likes

  • 🏳️‍⚧️ Ⓐ ♀ artbysekai ♀ Ⓐ 🏳️‍⚧️'s profile picture

    @tsisartbysekai

    tryna pull a calif on us

    2 likes

  • Iris's profile picture

    @lonelytransgrl8

    >uses stock android on a pixel ?????

    1 like

  • xergs's profile picture

    @xexif49197

    mentally ill activities right here, go find a job you f*g

    1 like