Notepad++ supply chain attack breakdown
securelist.com
Notepad++ supply chain attack breakdown
1–10 of 205 posts
Re: Notepad++ supply chain attack breakdown
#2It now seems to be best practice to simultaneously keep things updated (to avoid newly discovered vulnerabilities), but also not update them too much (to avoid supply chain attacks). Honestly not sure how I'm meant to action those at the same time.
Re: Notepad++ supply chain attack breakdown
#3I am running a lot of tools inside sandbox now for exactly this reason. The damage is confined to the directory I'm running that tool in.
There is no reason for a tool to implicitly access my mounted cloud drive directory and browser cookies data.
Re: Notepad++ supply chain attack breakdown
#4The article starts out by saying that Notepad++ "is a text editor popular among developers". Really?
Re: Notepad++ supply chain attack breakdown
#5> cmd /c "whoami&&tasklist&&systeminfo&&netstat -ano" > a.txt
Naive question, but isn't this relatively safe information to expose for this level of attack? I guess the idea is to find systems vulnerable to 0-day exploits and similar based on this info? Still, that seems like a lot of effort just to get this data.
Re: Notepad++ supply chain attack breakdown
#6It now seems to be best practice to simultaneously keep things updated (to avoid newly discovered vulnerabilities), but also not update them too much (to avoid supply chain attacks). Honestly not sure how I'm meant to action those at the same time.
[deleted]
Re: Notepad++ supply chain attack breakdown
#7It now seems to be best practice to simultaneously keep things updated (to avoid newly discovered vulnerabilities), but also not update them too much (to avoid supply chain attacks). Honestly not sure how I'm meant to action those at the same time.
I feel like supply chain attacks are the much rarer situation than real world exploits but I don’t have numbers.
Re: Notepad++ supply chain attack breakdown
#8It now seems to be best practice to simultaneously keep things updated (to avoid newly discovered vulnerabilities), but also not update them too much (to avoid supply chain attacks). Honestly not sure how I'm meant to action those at the same time.
Unless there's an announcement of a zero day, update a month after each new release. Keeps you on a recent version while giving security systems and researchers time to detect threats.
Re: Notepad++ supply chain attack breakdown
#9The article starts out by saying that Notepad++ "is a text editor popular among developers". Really?
LOL I guess the editors using Notepad++ downvoted you :P
Re: Notepad++ supply chain attack breakdown
#10The article starts out by saying that Notepad++ "is a text editor popular among developers". Really?
Literally yes: https://survey.stackoverflow.co/2025/