GoWard
sliver
GoWard | sliver | |
---|---|---|
2 | 20 | |
159 | 7,781 | |
- | 2.7% | |
0.0 | 9.6 | |
over 2 years ago | 3 days ago | |
Go | Go | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GoWard
sliver
-
With VPN's such as Twin Gate and TailScale, why open ports to expose services to the internet?
IDK if you are too young to remember the fallout from Snowden, but the Kremlin threw out entire rooms computers and for a time used actual typewriters. Because those computers had, more or less, twingate connectors on them. That's a bit of a rich example, but you're essentially installing what sliver calls an implant, what meterpreter calls a payload, and what Cobalt Strike calls a beacon. It's cool if you want to, but there's no need when you can just open a port with the same technology a Fortune 50 does.
- Sliver Release v1.5.40 - This release fixes a vulnerability (CVE-2023-34758) in the Sliver Key Encapsulation Mechanism (KEM), where improper use of Nacl Box (libsodium) could allow a MitM attacker with a copy of the implant binary to recover the session key and arbitrarily encrypt/decrypt C2 message
-
why no new Armitage :(((
What they said. Also, if you want a free alternative to cobalt: https://github.com/BishopFox/sliver
-
Suggestions for C2 server implementation
Sliver is neat, https://github.com/BishopFox/sliver
-
Cobalt Strike Alternative?
Armitage is precursor to CS but they diverged a long time ago. I ran up the armitage that comes with Kali these days, it has issues and bugs that would prevent it being useful. Sliver is probably the most usable FOSS C2. https://github.com/BishopFox/sliver
-
What's your preferred C2 / framework and why?
I’m a huge fan of Sliver, super powerful and well written/maintained with a lot of care and attention paid to tradecraft. I’m a big fan of the features like the built-in support for DNS canaries to detect blue team analysis. Only downside is that the documentation may be a little lacking.
- Sliver - an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver's implants support C2 over Mutual TLS, WireGuard, HTTP(S), and DNS and are dynamically compiled with per-binary asymmetric encryption keys.
-
External DNS Pentest
- https://github.com/BishopFox/sliver/wiki/DNS-C2
-
Evaluating Security Tools
For the additional more advanced steps I used sliver as a c2. Sliver is an excellent tool for the job and unlike some other tools, it's FOSS! You can easily replace sliver with your tool of choice, however.
- Sliver C2 Framework v1.5.11 released - as used by the Russian SVR - documented by NCSC, CISA, FBI and NSA in May 2021
What are some alternatives?
smtprelay - Simple Golang SMTP relay/proxy server
Empire - Empire is a PowerShell and Python post-exploitation agent.
easegress - A Cloud Native traffic orchestration system
Mythic - A collaborative, multi-platform, red teaming framework
athens - A Go module datastore and proxy
merlin - Merlin is a cross-platform post-exploitation HTTP/2 Command & Control server and agent written in golang.
SpoofDPI - A simple and fast anti-censorship tool written in Go
venom - venom - C2 shellcode generator/compiler/handler
ScareCrow - ScareCrow - Payload creation framework designed around EDR bypass.
empire - A PaaS built on top of Amazon EC2 Container Service (ECS)
BLUESPAWN - An Active Defense and EDR software to empower Blue Teams
zerotier-dns - A DNS server for ZeroTier virtual networks.