Angehefteter Tweet
1‘dave
225 posts
1‘dave
@d4ve415
tech stuff, learning, future role: security engineer, open to challenges and networking.
kernel Beigetreten Nisan 2025
83 Folgt55 Follower
Interviewer:
You use private browsing mode on a public computer.
Why can the next user still see your search history?🤔
English
1‘dave retweetet
fun fact: my first contribution was to the microsoft repository. You can see how much respect i had to them. Now I'm just loosing hope = ( . I hope @github @MsftSecIntel @Microsoft will bring my hope back. Lets see.
English
@5mukx @vxunderground
This is ridiculous. flagged for “malware” even though he was sharing public, legal PoC security tools and research.
It's discouraging that many years of research has gone down the drain over an allegation.
@github @Microsoft @MsftSecIntel
English
1‘dave retweetet
I request the community to share this issue and help me resolve it.
This is a major concern: sharing legal, open-source, public proof-of-concepts is now considered illegal?
Is helping the open-source security community now against the terms of service?
Or is this the new normal?!
2026 is causing a lot of trouble for security researchers.
I'm trying my best to follow the ToS, rules, and regulations of @github, @MsftSecIntel, and @Microsoft, but I'm starting to lose hope in conducting research, submitting vulnerabilities now..
Really i saw this on today morning and i am very disappointed. I have an little hope @github @MsftSecIntel @Microsoft.
Smukx.E@5mukx
Honestly, what is this ? I got a response from @github support team. So here after legal Security Research and PoC's is not allowed on GitHub ? I'm Completely got disappointment by @github and @Microsoft @MsftSecIntel . In what ways i distribute and share malware. Can anyone tell me if there is a mistake from my side, did i share 0 days, vulnerabilities, direct binaries or full exploit chain that harm users ? NONE ? is posting Legal source codes and tools that are made of public PoCs are wrong ? there are thousand of full chain real expoits that bypasses EDRs, C2s that evades security solutions, phishing kits that bypasses MFA of Microsoft out there in @github , if that is legal then why cant this simple publically made poc can't be in the github ? I have replied regarding my statements, please don't disappoint younger legal windows security researchers like this. I have some little hope on @github @Microsoft @MsftSecIntel . I have a little hope. So Please don't make me loose on @github & @Microsoft & @MsftSecIntel . Ticket ID: #4440743 Will be waiting for your kind response. Thank you. x.com/5mukx/status/2… #github #microsoft #security #research
English
1‘dave retweetet
Honestly, what is this ? I got a response from @github support team. So here after legal Security Research and PoC's is not allowed on GitHub ?
I'm Completely got disappointment by @github and @Microsoft @MsftSecIntel .
In what ways i distribute and share malware. Can anyone tell me if there is a mistake from my side, did i share 0 days, vulnerabilities, direct binaries or full exploit chain that harm users ? NONE ?
is posting Legal source codes and tools that are made of public PoCs are wrong ? there are thousand of full chain real expoits that bypasses EDRs, C2s that evades security solutions, phishing kits that bypasses MFA of Microsoft out there in @github , if that is legal then why cant this simple publically made poc can't be in the github ?
I have replied regarding my statements, please don't disappoint younger legal windows security researchers like this. I have some little hope on @github @Microsoft @MsftSecIntel .
I have a little hope. So Please don't make me loose on @github & @Microsoft & @MsftSecIntel .
Ticket ID: #4440743
Will be waiting for your kind response. Thank you.
x.com/5mukx/status/2…
#github #microsoft #security #research
English
1‘dave retweetet
English
TEST YOUR LINUX KNOWLEDGE
What does rm -rf do?
A. Rename files recursively
B. Delete files/directories recursively without prompts
C. Repair a filesystem
D. Read file contents
English
@davidbombal @Cisco It's my dream to be here too and to meet you too David.
English
1‘dave retweetet
Great people, great conversations, and an unforgettable time at Cisco Live! Always good connecting with the community and sharing moments like these.
Big thank you to @Cisco for making this trip possible!
English
1‘dave retweetet
Happy Birthday to me🎉🎉🎉
A year older, A year stronger.
This year, I'm focusing on growth, consistency, and becoming better at Cybersecurity every day.
Looking forward to more learning, opportunities, and success ahead. 🚀
English
1‘dave retweetet
As promised Rustypacker has released today.
A native Rust shellcode packer with a GUI
Repo:- github.com/Whitecat18/Rus…
What did I bring to the table :-
- Indirect syscalls for memory allocation and protection by default.
- AES-256-CBC, XOR, UUID-encoded shellcode encryption.
- Six self-injection paths through callback APIs.
- Fiber switch self injection.
- Three remote-process injection.
- Anti-debuging Techniques.
- NtDelayExecution sleep evasion with placement control.
- Domain pinning evasion.
- Output formats: EXE, DLL, DLL Sideload (Sideload or Proxy with auto-generated .def for unhandled
exports).
- Builds for x86_64-pc-windows-msvc and x86_64-pc-windows-gnu.
- DllMain stays a NO-OP. Payload rides four COM-friendly exports: Run, DllRegisterServer,
DllGetClassObject, DllUnregisterServer.
- crt-static link. No runtime DLL footprint.
- XOR-obfuscated NT API names embedded in the binary.
- Generated target/ auto-cleaned after each successful build.
#redteam #malwaredev #rust #offsec #infosec #windbg
English
1‘dave retweetet
One of the challenges I faced when integrating this feature. In RustyPacker you can generate proxy DLLs and sideloads with a single click. Try it out and let me know your feedback !
If you are interested in contributing your own techniques or fixing bugs, Please refer #contribution section in the repository.
Smukx.E@5mukx
As promised Rustypacker has released today. A native Rust shellcode packer with a GUI Repo:- github.com/Whitecat18/Rus… What did I bring to the table :- - Indirect syscalls for memory allocation and protection by default. - AES-256-CBC, XOR, UUID-encoded shellcode encryption. - Six self-injection paths through callback APIs. - Fiber switch self injection. - Three remote-process injection. - Anti-debuging Techniques. - NtDelayExecution sleep evasion with placement control. - Domain pinning evasion. - Output formats: EXE, DLL, DLL Sideload (Sideload or Proxy with auto-generated .def for unhandled exports). - Builds for x86_64-pc-windows-msvc and x86_64-pc-windows-gnu. - DllMain stays a NO-OP. Payload rides four COM-friendly exports: Run, DllRegisterServer, DllGetClassObject, DllUnregisterServer. - crt-static link. No runtime DLL footprint. - XOR-obfuscated NT API names embedded in the binary. - Generated target/ auto-cleaned after each successful build. #redteam #malwaredev #rust #offsec #infosec #windbg
English
1‘dave retweetet
