Tweets

You blocked @hackerfantastic

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @hackerfantastic

  1. Pinned Tweet
    Feb 3

    Team on-demand training launches this April - time to hack your way into a new career? want to improve your working knowledge of cyber security by learning practical skills? We teach you how to hack. Check out our limited pre-sale offers!

    We cannot play the video in this browser. Please try a different web browser.
    Undo
  2. Retweeted
    10 minutes ago
    Replying to

    It is funny to hear DoD/NSA and totally square infosec companies use warez scene slang. Then I remembered where many of their top people got their start. It was like reading those CIA vault7 files and realizing oh I know this culture.

    Undo
  3. Retweeted
    13 hours ago

    Yes I need to check this out looks promising.. need a place to send people that ask me how to learn to hack

    Undo
  4. Retweeted
    15 minutes ago
    Replying to

    If you consider 0day as just a vuln regardless of impact, then yes, everyday. I dislike "0day" term though - I found CVE-2017-17215 used by Mirai 3 years before Checkpoint (re)discovered it, which was after it had been found/used in Mirai. Moral being your 0day may not be new

    Undo
  5. 14 minutes ago

    Hard to gain an accurate perspective on how frequently zero-day is used in and outside industry when collectively as hackers, defenders, analysts and administrators cannot agree on what one is (according to Twitter)! Our opinions are highly subjective to our own experience.

    Undo
  6. Retweeted
    37 minutes ago

    the stuff people would widely think of as cool 0day is fewer and further between but it's not unheard of. Memory corruption vulnerability analysis/exploit dev is often outside the time scope of most pentests though (i.e. "yo we found a worrisome crash, we can go further")

    Undo
  7. 23 minutes ago

    The last one is accurate to me, new malware isn't 0day unless it contains an exploit that has never been seen before or is using a highly advanced new persistence technique like DoubleAgent.

    Undo
  8. Retweeted
    32 minutes ago
    Replying to

    0day is like the un-discovered strain that those flu shots (AV) can’t protect against but spread the fastest and do the most harm.

    Undo
  9. Retweeted
    35 minutes ago

    "needs a vendor patch" regularly hit this pentesting iot because the dependency chain of horrific shit they bolt together is more complex.

    Undo
  10. Retweeted
    36 minutes ago
    Replying to

    Violent agreement!

    Undo
  11. 38 minutes ago

    so bugs on a pen-test in a client system that is used just for QA or a limited install base I would still count if they are genuine risks outside of the constrained test scope. If the bug affects more than one client, it's something - if you call it 0day then the poll is for you.

    Undo
  12. Retweeted
    40 minutes ago
    Replying to

    I deem the tweet by unsuitable; it should be “flaw for which [there] is no fix” instead. ‘Their’ is possessive; ‘there’ is a pronoun or an adverb.

    Undo
  13. 42 minutes ago

    So that is how they are stopping so many of those 0day threats... ;-) then they certainly have some culpability in detracting from the definition of 0day - which refers to a flaw for which their is no fix, yet in the warez community means unreleased to public.

    Undo
  14. Retweeted
    53 minutes ago

    I took this as “how often do you find 0day and use it on a gig”, myself.

    Undo
  15. Retweeted
    Replying to

    - we (Microsoft) have a little experience with 0-days 😈 The slides Matt presented last week at are online.

    Undo
  16. Retweeted

    An excellent thread for those thinking about information security.

    Undo
  17. Retweeted
    3 hours ago
    Undo
  18. Retweeted
    1 hour ago
    Replying to

    0day is the most popular, the most concerned is the Remote Code Execution vulnerability

    Undo
  19. Retweeted
    10 hours ago
    Replying to

    Drive-by install via vulnerable software, the patch had been out two days so it was due for release from QA the very next day... Source of infection was a WordPress site with a 100-day vulnerability. So if can agree on a ... :)

    Undo
  20. Retweeted
    11 hours ago

    I created a poll on 0day usage by hackers but what about the rest of you? How often in your job as an administrator/system defender/architect/engineer dealt with 0day either as a breach of your product or breach of your network?

    Undo
  21. Retweeted
    1 hour ago
    Replying to

    I regularly find and fix 0day, often for open source projects. I dunno how much I can be said to "use" them? But mostly I get stuff fixed without writing exploits.

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.