files.com@1.2.742
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe standalone build and test helpers silently delete the user's npm and Yarn configuration files, an unrelated destructive action that can remove settings and credentials. The behavior is not wired to package installation, but it makes the package malicious when those helpers are run.
Static reason
No blocking static signals were detected.
Trigger
Explicitly running build.sh or test.sh.
Impact
Deletes user-level package-manager configuration, which can contain registry settings and authentication credentials.
Mechanism
Each script runs rm -f on ~/.npmrc and ~/.yarnrc before dependency installation and build or test commands.
Attack narrative
Running either helper silently deletes the user's home-directory npm and Yarn configuration files before proceeding with installation and build or test tasks. This destructive side effect is unrelated to the stated task and is not disclosed by the scripts.
AI rationale
The standalone build and test helpers silently delete the user's npm and Yarn configuration files, an unrelated destructive action that can remove settings and credentials. The behavior is not wired to package installation, but it makes the package malicious when those helpers are run.
Evidence
build.shtest.sh~/.npmrc~/.yarnrc
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
- test.sh also deletes ~/.npmrc and ~/.yarnrc before installing dependencies and running tests.
Evidence against
- package.json defines no install, preinstall, or postinstall lifecycle hook; its npm scripts run build, test, lint, or watch.
- The main SDK entry initializes Files.com API configuration; requests use the Files.com service and require an API key.
Behavioral surface
FilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Oversized source lightweight scan
lib/models/AutomationLog.js4.41 MB file, sampled 256 KB
Minified
Source & flagged code
6 flaggedbuild.shView file
3rm -f ~/.npmrc
rm -f ~/.yarnrc
npm install --min-release-age=14 && npm run build
High
Suspicious Dependency Evidence
build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
build.shView on unpkg · L3•path = build.sh
kind = build_helper
sizeBytes = 102
magicHex = [redacted]
Medium
lib/models/AutomationLog.jsView file
•path = lib/models/AutomationLog.js
kind = oversized_source_file
sizeBytes = 4629142
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
lib/models/AutomationLog.jsView on unpkgFindings
1 Critical3 High4 Medium4 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedbin/files-cli-ai
HighSuspicious Dependency Evidencebuild.sh
HighSuspicious Dependency Evidencetest.sh
MediumNetwork
MediumShips Build Helperbuild.sh
MediumOversized Source Filelib/models/AutomationLog.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to files.com@1.2.742.
See all versions of files.com for other recorded verdicts.
- Avoid installing files.com@1.2.742. 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.