Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell) header
Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell) profile picture

Cyber Security Manager ๐Ÿ’ป | Public Sector | #CISSP | #CCSP | #SecurityX | #Pentest+ | #CySA+ | #CyberSecurity | #Infosec | #Hacking

/dev/null
Joined April 2018
Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)Photo by Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ (@d4rkshell)
Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ retweeted
Kali Linux 2026.โ€‹3 Release (Build-Scripts Refresh): We are back with Kali Linux 2026.โ€‹3, the third release of the year! We have been busy making it easier to build Kali, updating the desktop experience, and bringing in more toolsโ€ฆ www.โ€‹kali.โ€‹org/blog/kali-linux-2026-3-release/
30
195
19
1,366
69,321
Well, it's certainly been an interesting week in the #Cyber world! Oof.
56
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
332
16,448
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
85
10
487
951,376
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
70
Tickets acquired and accommodation booked for @BSidesLondon ๐Ÿ˜ƒ
1
4
255
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
335
31
1,750
206,947
Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ retweeted
Shodan Membership sale is live until 2026-08-09 00:00 UTC (~48 hours from now): account.shodan.io/billing/meโ€ฆ
77
487
109
1,437
501,725
Christopher | ๐Ÿ‡บ๐Ÿ‡ฆ ๎จ€ retweeted
From a normal domain user to Domain Admin, bypassing the SID patch. ESC1 is alive again, under some conditions. MSRC closed it as โ€œBy design.โ€ Writeup and PoC below, judge for yourself. 0xmaz.me/posts/certsrv-id-cmโ€ฆ
5
73
7
250
29,188
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
154
6
779
56,054
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
492
๐Ÿšจ 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
704
1,573
553
14,900
3,568,421
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
698
103
3,747
879,196
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
This claim, however comes after they threatened to take legal action against Nightmare Eclipse a security researcher, over Zero Day exploits. The security researcher was also banned on Github for their research and a consequent ban from Gitlab as well. theverge.com/tech/940416/miโ€ฆ tomshardware.com/tech-industry/โ€ฆ
291
103
162
469
599,900
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])
36
341
14
2,017
103,343
Update: account is now showing as blocked on GitLab ๐Ÿ˜ข
1
4
1,000