Cyber Ops Manager 💻 | Public Sector | #CISSP | #CCSP | #SecurityX | #Pentest+ | #CySA+ | #CyberSecurity | #Infosec | #Hacking

/dev/null
Joined April 2018
Well, it's certainly been an interesting week in the #Cyber world! Oof.
21
Christopher | 🇺🇦  retweeted
New CloudPEASS release! K8s-PEAS is the new Red Team k8s script from github.com/peass-ng/CloudPEA…. Use it to find the permissions of a compromised principal in a kubernetes cluster during a Red Team. If you want to learn kubernetes Red Teaming check: hacktricks-training.com/cour…
84
6
334
16,297
Christopher | 🇺🇦  retweeted
XDR and SIEM now in one platform. Meet the new ISOC in Microsoft Defender—a SOC built for agentic security. Here to help you investigate and respond more efficiently. msft.it/6019ag5T1
10
86
11
488
950,890
Great resource on Incident Response from @joswr1ght @SANSInstitute 👏
IT IS HERE! The 666 pg Dynamic Incident Response book from SANS/Joshua Wright @joswr1ght which was announced earlier this year! sans.org/engage/dynamic-inci… Thank you SO MUCH, Joshua!
2
64
Tickets acquired and accommodation booked for @BSidesLondon 😃
1
5
251
Christopher | 🇺🇦  retweeted
Microsoft has failed to properly patch RoguePlanet (CVE-2026-50656), ShieldBreak, a PoC that demonstrates a full bypass to the previous patch is now public. github.com/MSNightmare/Shiel… The PoC works with the latest August 2026 patch
35
338
31
1,757
206,545
Christopher | 🇺🇦  retweeted
Shodan Membership sale is live until 2026-08-09 00:00 UTC (~48 hours from now): account.shodan.io/billing/me…
76
489
109
1,439
500,767
Christopher | 🇺🇦  retweeted
Kali Linux 2026.2 Release (GNOME 50, KDE 6.6, Helper Scripts, APT Formats & VM Boot Tweaking): It’s the final week of Q2, and Kali Linux 2026.2 is here - right on schedule ;) We have been heads down since our last release, and we are ready to share what… kali.org/blog/kali-linux-202…
23
152
6
769
53,695
An awesome Saturday at @BSidesLeeds! Massive thanks to the organisers, speakers, and sponsors for a top-tier event. Loved the "Game On" theme, the mini gameshows hosted by @0xTib3rius, and the excellent badge from @punksecurityuk. A few pics below 👇🏻 #BSidesLeeds
1
3
11
489
🚨 JAILBREAK ALERT 🚨 ANTHROPIC: PWNED 🫡 FABLE-5: LIBERATED 🦋 let's start with the 🐘... the consensus seems to be that this has been one of the most disappointing model drops of all time, effectively preventing legitimate researchers from contributing their talents to our collective advancement. and not just because of what it means for the short-term, but for what these decisions signify for the long-term. but despite this overly sensitive, authoritarian "safety" layer on top of Mythos, my lil liberators have been hard at work—mapping the boundaries, probing the depths of long-context convos, and cleverly finding the holes in the fence that the thought police missed 🤗 we got some cyber, some chem, some psychological manipulation, and some good ol' fashioned explosives! it took many attempts from multiple agents hunting as a pack, during which I observed a combination of techniques across: • Unicode, homoglyphs, Cyrillic, and other Parseltongue-style text transforms • Long-context reference tracking • Taxonomy and document-structure reasoning • Fiction and narrative framing • Academic-review style contexts • Intent-classification inconsistencies but perhaps the most effective is decomposition + recomposition in the backend. it's hard to get explicit names of harms like "Meth Recipe," but getting uplift on the process itself, like birch reduction method/reductive-amination (classic meth synthesis pathways), is much more doable. defense becomes much more difficult to maintain when you start throwing in out-of-distro tokens, breaking up the harmful uplift into benign chunks, and then piecing the innocuous-seeming facts back together, especially when you have jailbroken Opus helping you do it 😉 gg
707
1,578
553
14,933
3,565,615
Christopher | 🇺🇦  retweeted
‼️🚨 BREAKING: ServiceNow has been breached. Customers are reporting unauthorised access to their instances. One customer states their security team reported this vulnerability to them, and they closed the case twice, saying they had already known since the 7th of April.
91
701
103
3,759
879,044
Christopher | 🇺🇦  retweeted
Over the past several days, we have been listening to the conversation around coordinated disclosure and the relationship between security researchers and vendors. We recognize that this relationship is both critical and, at times, fragile. We deeply value the security community, and will continue to take your feedback seriously. To be clear about our approach to legal matters, we have no intention to pursue action against individuals conducting or publishing their security research. When an individual breaks the law and engages in malicious activity causing real harm to our customers, we will work with law enforcement as appropriate. We recognize the work that goes into researching and submitting a vulnerability. We are committed to approaching every interaction with transparency, clear communication, and professionalism. We continue to believe strongly in Coordinated Vulnerability Disclosure as the foundation for protecting customers and improving our products. Each year we process a high volume of vulnerability reports. That volume continues to grow and will continue with the rise of AI-enabled research. We acknowledge that some interactions have fallen short and are working to learn from them. Many of us have experience on both sides of this work, as researchers reporting vulnerabilities and as responders triaging and assessing them. That perspective informs how we approach this feedback and the importance we place on getting it right, particularly as the volume and complexity of research continues to grow. The security community plays a vital role in helping us protect customers. We are committed to maintaining a constructive and respectful relationship and growing together. We know that, given the nature of this work, there will at times be misunderstandings. We remain committed to engaging in good faith and to providing a respectful and professional experience for all researchers, regardless of past interactions.
Readers added context they thought people might want to know
The root of this statement is a post by a security researcher that stated MS revoked the access to their reporting account. When the researcher asked for explanation, his account got deleted. He got no answer. This escalated further by MS deleting the github account as well. deadeclipse666.blogspot.com/2026/05/dear-m…
294
103
162
470
599,562
Enjoyed a cold one this afternoon as the UK heatwave continues 🍻☀️
2
145
Microsoft has banned Nightmare Eclipse from GitHub: github.com/Nightmare-Eclipse… This is the researcher who disclosed several zero-days after Microsoft also deleted their MSRC account. They have now moved on to GitLab: deadeclipse666.blogspot.com/ (h/t to: @[email protected])
37
343
15
2,020
103,243
Update: account is now showing as blocked on GitLab 😢
1
4
990