josh
josh
josh@westernbtc.com
npub1pc57...dmza
Loved by Jesus
Join the https://westernbtc.com relay if you want all your notes backed up.
nostr:nevent1qqspstxd0rrl9ymfg53g70p0xucj7t8y6a4wn793m3prpaa37hrhgdc5w723t
nostr:note1etztafg2td6e7fal9373qj88ykuuvdyzdlaqm59ttcqamga5nr3sh9xgry
UPDATE:
Regarding my loss of ~0.2 bitcoin, I believe I found the attack vector used by the perpetrator.
In March of 2025, a K8 vulnerability was disclosed: IngressNightmare (CVE-2025-1974). This allows an attacker to gain full RCE of a pod, and therefor, gain access and control of the internal network. A CVSS 9.8 vulnerability.
I feel slight relief knowing that this is *likely* how the attacker gained access to my internal network.
There were many mistakes on my part, and those will be what I focus on significantly improving.
What do you use for your personal laptop and personal phone? I'm contemplating switching.
Helpful tip: use a virtual card for every subscription. If any service makes it difficult to cancel, simply delete the virtual card.
“Don’t sin by letting anger control you. Think about it overnight and remain silent. Interlude”
Psalms 4:4
Yesterday was brutal. From this point, I see two paths forward.
Sit in self pity and stay down.
See this as an opportunity from God.
It could have been worse. This is an opportunity to look inward and see my flaws. Not leave it there, but be honest. I was careless with security. I thought: "this probably won't happen to me". I didn't have: alerts in place, proper logging, kill switches, separation of responsibility, on and on.
I pray this won't be a lesson I ever have to learn again.
Learn this lesson from me: it CAN happen to you.
I still have no idea how the attacker was able to get access to my lnd node. I messed up a in few ways with protecting my admin macaroon, but the unknown is what bothers me the most.
View quoted note →
