registry / Destructive action / credstore
credstore
Secure Offline Credential Manager
This report shows the evidence for credstore@1.1.24. 2 of 7 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms an unconsented install-time destructive action against the package's stored credential data. No exfiltration was found, but the automatic vault deletion warrants blocking.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install or update
Impact
loss of locally stored credential vault data
Mechanism
automatic recursive deletion of user application-data paths
Attack narrative
The postinstall lifecycle command passes --install to clean-vault.js. That flag enables deletion without confirmation, and the script recursively removes CredStore-named configuration, cache, and data directories across supported platforms. For a credential manager, silently wiping existing vault data during package installation is concrete destructive behavior; the separate Linux launcher creation does not mitigate it.
AI rationale
Source inspection confirms an unconsented install-time destructive action against the package's stored credential data. No exfiltration was found, but the automatic vault deletion warrants blocking.
Evidence
package.jsonscripts/clean-vault.jselectron/main.jsscripts/postinstall-desktop.js
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json postinstall invokes clean-vault.js --install --quiet.
- scripts/clean-vault.js treats --install as automatic --yes.
- The script recursively removes CredStore config, cache, data, and desktop files.
- Deletion runs during npm postinstall without a user cleanup command.
Evidence against
- No credential-harvesting or remote exfiltration path found.
- electron/main.js blocks non-local renderer requests in production.
- Runtime networking is OTP-gated local-LAN sync only.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedObfuscatedUrlStrings
CopyleftLicense
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/clean-vault.js --install --quiet && node scripts/postinstall-desktop.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/clean-vault.js --install --quiet && node scripts/postinstall-desktop.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/credstore.jsView file
2L3: const { spawn } = require("child_process")
L4: const fs = require("fs")
High
Findings
5 High4 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/credstore.js
HighShell
HighSame File Env Network Executionelectron/main.js
HighPrevious Version Dangerous Deltaelectron/main.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowObfuscated
LowHigh Entropy Strings
LowUrl Strings
LowCopyleft License
Affected versions and remediation
This report applies to credstore@1.1.24.
The versions list below shows the verdict for each recorded version.
- Avoid installing credstore@1.1.24. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.