milliways-infosec/BlueHammer
7
0
Fork 0
mirror of https://github.com/Nightmare-Eclipse/BlueHammer.git synced 2026-05-26 11:50:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
Repository hosting the bluehammer vulnerability
4 commits 1 branch 0 tags 621 KiB
Find a file
Nightmare-Eclipse 6222eacb22
Update README.md
2026-04-03 03:19:28 +02:00
x64/Release Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.aps Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.cpp Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.rc Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.sln Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.vcxproj Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.vcxproj.filters Initial commit 2026-04-03 01:40:42 +02:00
FunnyApp.vcxproj.user Initial commit 2026-04-03 01:40:42 +02:00
LICENSE Initial commit 2026-04-03 01:38:24 +02:00
offreg.h Initial commit 2026-04-03 01:40:42 +02:00
offreg.lib Initial commit 2026-04-03 01:40:42 +02:00
README.md Update README.md 2026-04-03 03:19:28 +02:00
resource.h Initial commit 2026-04-03 01:40:42 +02:00
windefend.idl Initial commit 2026-04-03 01:40:42 +02:00
windefend_c.c Initial commit 2026-04-03 01:40:42 +02:00
windefend_h.h Initial commit 2026-04-03 01:40:42 +02:00
windefend_s.c Initial commit 2026-04-03 01:40:42 +02:00

README.md

BlueHammer

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

Repository hosting the bluehammer vulnerability

I'm just really wondering what was the math behind their decision, like you knew this was going to happen and you still did whatever you did ? Are they serious ?

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCac8VlgAKCRDFFoRCS0/S bK8pAP9CzNnH26FVVdHZWVyDvOIwuZ1np1dTv7T5YaVCjf4tiwD+MC4Ikq+/ywdD I7dabkH7iSZflULM+hGUOur0mnAg9Qw= =Enhh -----END PGP SIGNATURE-----