https://xitter.cf/t.co/BycBKeVgps

Joined April 2024
silentwarble retweeted
The TL;DR of what Anthropic just said: 1.) GLM-5.3 is as good as Mythos for exploit development. 2.) Unlike Claude, GLM-5.3 gives you the results you pay for. 3.) Governments should ban AI models which are as good as theirs but are not made by them. The funniest part is how Anthropic admitted self-reflectively that the lack of guardrails may actually be benefiting the defenders working to secure their systems. 🤪 Something they never wanted to allow, because of possible misuse. I don't get it, but I feel Anthropic should at least put a note at the very bottom if they are doing paid advertising to promote GLM-5.3. 😜 Source: anthropic.com/research/glm-5…
37
172
12
1,398
56,400
silentwarble retweeted
We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money. ARM hardware memory tagging (MTE) is used by GrapheneOS across the entire base OS including the kernel and every standard base OS process. It's only temporarily disabled for a few device-specific processes. It greatly improves protection against nearly all remote exploits and many local exploits. Pixel 8 launched with hardware MTE support in October 2023. We integrated it into our hardened_malloc project and began using it across the OS later that month. Android and the Pixel OS never started using it by default. Android Advanced Protection Mode in Android 16 enables it for a few processes. Apple's Memory Integrity Enforcement (MIE) is an always enabled feature on the iPhone 17. It's simply a high quality implementation of MTE using the latest standard extensions. It uses MTE in the most secure mode in the kernel and a large portion of userbase. They did a very good job integrating it. Apple's MIE and Android 16+ AAPM don't use MTE for user installed apps unless those explicitly opt in. GrapheneOS enables it for more apps automatically and has a toggle for users to opt-in for every user installed app. There's a per-app toggle to opt-out for incompatible apps which is uncommon. Neither iOS or Android encourage app developers to opt into MTE and other more aggressive security features used in the base OS. Apple's docs warn developers of performance and stability issues. Even Signal doesn't opt-in. Our approach enables forcing using MTE in the standard allocators regardless. Pixel 11 does have security improvements including moving to post-quantum secure verified boot (ML-DSA) and replacing Samsung Shannon IMS with AOSP IMS. Titan M3 should significantly improve protection against data extraction in Before First Unlock state. It's too bad they ruined it by cutting MTE. Pixel 11 series is a lot more expensive for an incremental improvement to the CPU, the same underpowered GPU and reduced RAM for the Pro base models. They finally caught up to the last generation of Qualcomm cellular radio. It's overpriced, the upgrades aren't impressive and losing MTE is appalling. Compared to the Pixel 11, a Snapdragon 8 Elite Gen 5 has ~40% higher single threaded CPU performance, ~80% higher multi threaded performance, over 100% higher GPU performance and a far better cellular radio. It also finally has MTE. The next gen is what will be in the first Motorola with GrapheneOS. Pixel 9a and earlier (including Nexus devices) were the Android Open Source Project reference devices. Pixel support was removed from AOSP with Android 16. It's now harder to support Pixels than many other devices and massive progress towards open source firmware and driver libraries was discarded. Compared to the stock Pixel OS, GrapheneOS ships AOSP patches months earlier and Linux kernel patches many months earlier. However, we rely on them for firmware and most driver updates. We also want to move to new kernel branches earlier. These things can be improved with our Motorola partnership. We strongly recommend against buying Pixel 11 devices. Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE. Pixel 11's Titan M3 should improve BFU security for users without a strong passphrase, but losing MTE craters AFU security. We haven't determined what to do about this situation. It may be best for us to skip the Pixel 11 series devices. We can shift our focus entirely to the upcoming Motorola devices instead. Pixel 10a was really a 9th gen Pixel, so hopefully the Pixel 11a does the same with 10th gen and includes MTE.
239
718
165
5,691
907,960
silentwarble retweeted
We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support. motorolanews.com/motorola-th…
645
1,761
446
12,655
1,134,934
Good stuff as always
The recording of our (CC @nicolodev) talk "Breaking Mixed Boolean-Arithmetic Obfuscation in Real-World Applications" at @reconmtl is now online! Recording: youtube.com/watch?v=QxSGWk3M… Slides: synthesis.to/presentations/r… #BinaryNinja Plugin: github.com/mrphrazer/obfusca…
184
silentwarble retweeted
lol whole new calling conventions for PIC literally a day after I release my kit 😅 aff-wg.org/2025/10/13/weedin…
1
22
102
8,545
silentwarble retweeted
We at @emproofsecurity open-sourced a free firmware reverse engineering workshop for self-study. Topics: ELF analysis, cracking, malware triage, embedded-Linux, bare-metal, crypto-key extraction, anti-analysis. Docker setup and solutions included. github.com/emproof-com/works…
83
1
315
20,852
silentwarble retweeted
We're really bringing the 🔥 with our next Nighthawk release - Janus - nighthawkc2.io/janus/
1
23
1
114
25,632
silentwarble retweeted
You can only score 100% ATT&CK coverage for so long xitter.cf/nickvangilder/status/1…
Replying to @eliedelkind
Microsoft: After extensive deliberation, Microsoft has decided to not participate in the evaluation this year. This decision allows us to focus all our resources on the Secure Future Initiative and on delivering product innovation to our customers. (techcommunity.microsoft.com/…’s-participation-in-mitre-attck®-evaluations-enterprise-2025/4422639) S1: This decision was reached after a thorough review internally and is being made so that we can prioritize our product and engineering resources on customer-focused initiatives while accelerating our platform roadmap. (sentinelone.com/blog/sentine…) Palo Alto: After thoughtful evaluation of our priorities, we have decided to adjust the focus of our engineering and testing resources and will not be participating in this year’s MITRE evaluation. This decision enables us to further accelerate critical platform innovations that directly address our customers' most pressing security challenges and respond even faster to the evolving threat landscape. (paloaltonetworks.com/blog/se…)
3
10
1
83
22,445
silentwarble retweeted
We've just pushed details on our latest #Nighthawk release (Sivako) nighthawkc2.io/sivako/ - including async BOF support, native kerberos and more 🔥 vimeo.com/1115201393?share=c…
5
22
2
87
28,400
silentwarble retweeted
Exciting times. I'm publishing Dittobytes today after presenting it at @OrangeCon_nl ! Dittobytes is a true metamorphic cross-compiler aimed at evasion. Use Dittobytes to compile your malware. Each compilation produces unique, functional shellcode. github.com/tijme/dittobytes
11
97
6
254
27,856
silentwarble retweeted
Do you want to trigger shellcode only when: - Certain DNS resolution happens? - Certain servers are reached out to? - When you get a 112 byte long response? ...etc Meet InternetSetStatusCallback() for fine tuning execution (or if you are just bored): gist.github.com/whokilleddb/…
5
97
432
26,652
Are you thinking of writing a C2? Do you want to modify an existing C2? Have you ever thought "why on earth did they do it that way"? Join me as I show what I've learned from 7 years of open source C2 and agent development so you can start off with success :) I can't wait!
9
1
46
3,043
silentwarble retweeted
New blog from me about a bug in Power Apps that allows execution of arbitrary SQL queries on hosts connected through on-prem data gateways. This can turn external O365 access into compromised on-prem SQL servers. ibm.com/think/x-force/abusin…
7
76
1
178
14,466
This continues to be a great tool. I'm using it to make stripped down throwaway VMs for when we do ops. Otherwise win11 is such a hog: github.com/ntdevlabs/tiny11b…
8
43
1,509
Ooh someone's taking notes. @SentinelOne If ya'll got any questions feel free to hit me up. Referrers hitting the Hannibal agent repo:
1
9
494
This has been a LONG time coming! This is just the beginning though :) I'll be recording more for updates, features, workflow updates, and yes - a developer series too! Be sure to let me know what you do/don't like about this format and what kinds of things you'd like to see!
Mastering Mythic doesn't have to be complicated. 😵‍💫 Check out our operator-focused video series w/ @its_a_feature_, which cuts through the noise & delivers exactly what you need to customize & leverage Mythic effectively. 👀: ghst.ly/mythic-op
1
19
70
4,719
silentwarble retweeted
As promised... this is Loki Command & Control! 🧙‍♂️🔮🪄 Thanks to @d_tranman for his work done on the project and everyone else on the team for making this release happen! github.com/boku7/Loki
27
238
1
705
573,100
silentwarble retweeted
Today I'm releasing Xenon, a custom Mythic agent for Windows targets written in C. Notable features include: 📁 Modular command/code inclusion 🦠 Malleable C2 Profile support 🪨 Compatible with Cobalt Strike BOFs github.com/MythicAgents/Xeno… Blog series - c0rnbread.com/creating-mythi…
6
90
1
284
19,444
If your org has MS 365 don't overlook PowerApps and Power Automate. I'm finding it to be quite useful for both nefarious and process purposes. Easier to deploy tooling in an already approved platform vs a custom webapp.
8
419