Re:Self Propagating NPM Malware Compromises over 40 Packages
by mr_toad on Tuesday September 16, 2025 @08:17AM
(#45261228)
One option is pass, which is a shell script that uses GPG to manage passwords for command line tools. You can put the password store into a git repository if you need to sync it across machines.
[ Parent
| on HN ]
Re:Self Propagating NPM Malware Compromises over 40 Packages
by chrisweekly on Tuesday September 16, 2025 @08:47AM
(#45261503)
Wait, what? "put the password store into a git repository"?!
Re:Self Propagating NPM Malware Compromises over 40 Packages
by dflock on Tuesday September 16, 2025 @10:13AM
(#45262528)
The store in the case of pass, is a plain text file, whose contents are encrypted strings. If you trust the encryption, you can put it anywhere you like. Keep the keys secret and safe, though!
Re:Self Propagating NPM Malware Compromises over 40 Packages
by 9dev on Tuesday September 16, 2025 @04:14PM
(#45267380)
Until you have to fire one of your disgruntled employees, who has a copy of all your secrets that you now need to rotate.
A repository that an attacker only needs to get access to once, after which they can perform offline attacks against at their leisure.
A repository that contains the history of changed values, possibly making the latter easier, if you used the same encryption secret for rotated values.
This is an awful idea. Use a proper secret management tool you need to authenticate to using OIDC or Passkeys, and load secrets at runtime within the process. Everything else is dangerous.