Posts
3259
Following
709
Followers
1567
"I'm interested in all kinds of astronomy."
repeated

Microsoft is investigating reports that some Windows 11 devices are failing to boot with "UNMOUNTABLE_BOOT_VOLUME" errors after installing the January 2026 Patch Tuesday security updates.

https://www.bleepingcomputer.com/news/microsoft/microsoft-investigates-windows-11-boot-failures-after-january-updates/

1
3
0
@halfbyte I'm with you and while I also believe deep in their hearts enterprise IT teams do want "robust and reliable" providers, I also have good reason to believe that C-level incentive to "avoid onboarding another provider with procurement and whatnot" is much stronger.

If you can't provide *everything* you will eventually be replaced with someone who does.
0
0
0
@hongminhee

In #Hungary:

Me: how come you don't take your shoes off?
US friend: *looks around* our streets are not full of dog shit
0
0
1
Demystifying CVE-2025-47987 [Heap-based buffer overflow in Windows Cred SSProvider Protocol LPE]

https://kryptoenix.github.io/blog/demystifying-CVE-2025-47987/
0
3
4
here's a video (this was the 3rd edition): https://www.youtube.com/watch?v=qMyvfnESJWU
0
0
0
Budapest Micro will be back in March with workshops and Chiptune \o/

https://www.scene.hu/2026/01/24/budapest-micro-vol3-2026-03-28-harom-hollo-budapest/

(I've been to a *lot* of different, often very extreme shows, but I will never forget the first Budapest Micro!)

#chiptune #demoscene #budapest
1
6
4
[RSS] Defeating Anti-Reverse Engineering: A Deep Dive into the 'Trouble' Binary

https://binary.ninja/2026/01/23/reversing-linux-anti-re.html

#ReverseEngineering
1
0
0
[RSS] [Blog] Unauthenticated RCE in NetSupport Manager - A Technical Deep Dive

https://code-white.com/blog/2026-01-nsm-rce/

CVE-2025-34164, CVE-2025-34165
0
2
1
repeated
Edited 7 hours ago

AMD4700S Root Key 0 SHA256: 95333bf313b67f653e2b80518d39e39cbc8f481f61a86f6052d2b277217206d3
AMD4700S Root Key 1 SHA256: e2e0e8f8e0c66339c28ed3ee66e2fc9499ac5a5332009f57df556b4b319a73a7
AMD4700S Root Key 2 SHA256: f87833eb4a152f25d07051e73b23a5923fa8ddbdac879940eb1703fa5f9a4d09
AMD4700S Root Key 3 SHA256: 5163e65a31dab1bb833802390dc0bc0d330c8592e20f31133f2be27dbec109b8

Hash values calculated using the raw key bytes. If you get something else, try reversing all key bytes.

0
5
0
One of my hinges broke (it supported a small, light door for whole 10 years...) and the only replacement I found would be from the UK manufacturer, wholesale, so I put on this great album:

https://www.youtube.com/watch?v=ktYn7OZCN4c&list=PLymNFxwBo3tjsy_HQdenCQ1K4a5hrHv9t
0
0
0
repeated

Graham Sutherland / Polynomial

stumbled into the Logitech subreddit and found out that Logitech's code signing certificate for macOS expired a few weeks ago, which caused Logitech Options+ to be unable to launch, which stopped everyone's mice from working until Logitech updated it.

so much stupid involved here.

2
3
1
repeated

There is an open position on my team:
https://crowdstrike.wd5.myworkdayjobs.com/en-CA/crowdstrikecareers/job/United-Kingdom---Remote/Security-Researcher--Malware-Triage--Remote-_R26466
While this is not currently listed here, I am certain that U.S. remote is an option and if you're in Canada, I strongly expect that this would work as well.

0
6
0
Raiden Warned About AI Censorship

https://www.youtube.com/watch?v=-gGLvg0n-uY

This is creepy af (2023!)
1
0
0
[RSS] Python Wheel (Zip) Parser Differential Vulnerability v2.0

https://github.com/google/security-research/security/advisories/GHSA-w97x-xxj5-gpjx
0
0
0
[RSS] Foxit, Epic Games Store, MedDreams vulnerabilities

https://blog.talosintelligence.com/foxi-and-epic-games/
0
0
0
repeated

“What if I Simply put tailscale in initramfs?”: statements dreamed up by the utterly deranged (that is, @jyn ). Very cool blog post on remotely unlocking an encrypted boot partition: https://jyn.dev/remotely-unlocking-an-encrypted-hard-disk/

1
9
0
repeated

So who at Argo CD is sleeping? 68 days old report of RCE with POC reported accordig to procedure as it should, tried poking slack, mail... No ack. Wondering if just full disclosure is the way. Please ping me, not my finding but will relay.

0
3
0
repeated

📣 Help needed! For our upcoming talk, @boblord and I are studying cyber near misses, moments where serious harm was narrowly avoided, and what we can learn from them. These near misses might apply to software development, or to network defense. (Please boost for reach! 🙏)

We are hoping to surface general patterns using some (anonymized) examples.

If you’re willing, reply with a high-level response to one or two of these prompts. Anonymize as appropriate, and/or send to us in DMs if you prefer:

* What lesson did an organization fail to learn after a near miss, even though it seemed obvious at the time?
* Describe a time when you discovered something and thought “If we didn’t catch this now, it would have been baaaaad”.
* Describe a time when you dealt with a software vulnerability in your systems that was being actively exploited elsewhere, but (as far as you could tell), not in yours. What saved the day?
* What repeated “almost failures” do you see getting normalized or waved away as acceptable risk?
* Can you recall a near miss triggered by a third party such as a researcher report, customer question, bug bounty submission, or vendor advisory that revealed a bigger issue than expected?
* Can you think of a near miss where the most important factor was not a security control, but a human action like someone double-checking, questioning an alert, or escalating a “weird feeling”?

Thanks!

0
6
0
Show older