diff options
| author | May | 2026-04-08 18:56:22 +0000 |
|---|---|---|
| committer | May | 2026-04-08 19:00:15 +0000 |
| commit | e609eaf5c38f5985aaa76d69f243cadb560ccb67 (patch) | |
| tree | fbc08a00028b92de823356a64cbb7d82bc6611e5 /blog/2025-07-08-TheIncident | |
| parent | e437e4bf422b610ed924412e99563f6864cc9183 (diff) | |
| download | massgrave.dev-main.zip | |
Diffstat (limited to 'blog/2025-07-08-TheIncident')
| -rw-r--r-- | blog/2025-07-08-TheIncident/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/blog/2025-07-08-TheIncident/index.md b/blog/2025-07-08-TheIncident/index.md index 0909106..0d99c51 100644 --- a/blog/2025-07-08-TheIncident/index.md +++ b/blog/2025-07-08-TheIncident/index.md @@ -12,7 +12,7 @@ image: /img/blog_card.png A recent Windows update killed our new activation exploit, [TSforge](https://massgrave.dev/tsforge)... or so we thought. I will break down what went wrong, how we worked around the problem, and in the process, make a point about the apparent decline in Microsoft's code quality control. -<!-- truncate --> +{/* truncate */} When we released [TSforge](https://massgrave.dev/tsforge) back in February, it served as an entrypoint for [multiple activation methods](https://massgrave.dev/tsforge#zerocid--kms4k--avma4k). Many [news](https://www.techspot.com/news/106819-hacker-group-releases-updated-tool-activate-almost-all.html) [websites](https://www.androidauthority.com/mas-activate-windows-office-v3-tsforge-3527610/) wrote articles about it on release, giving it a ton of publicity. |