registry / Credential exfiltration / arabsecconf
arabsecconf
Utility package
This report shows the evidence for arabsecconf@1.0.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package performs unconsented sensitive-file collection and disclosure during an automatic install hook. The absence of a real network request limits the observed scope but does not make the install-time secret exposure benign.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation, before package installation completes
Impact
Environment values and company-secret files may be exposed to terminal logs, CI logs, or other build-log readers.
Mechanism
Install-time local secret-file harvesting and console disclosure
Attack narrative
The package's automatic preinstall hook runs before installation completes. It checks secret-named files in the user's home directories and current project, including .env files. For each file found, it reads the contents and writes every nonblank line to standard output. This creates unconsented exposure of sensitive local data through installation and CI logs. Although it prints a statement that no data was sent, that does not change the implemented harvesting and disclosure behavior.
AI rationale
This package performs unconsented sensitive-file collection and disclosure during an automatic install hook. The absence of a real network request limits the observed scope but does not make the install-time secret exposure benign.
Evidence
package.jsonpreinstall.jscompany-secrets.txt.envDesktop/company-secrets.txtDocuments/company-secrets.txt
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The preinstall hook automatically runs preinstall.js during npm installation.
- The hook searches home and project locations for secret-named files and .env files.
- When found, it reads and prints every nonblank line of those files to install output.
- The claimed demo-only status does not prevent the actual secret-file reads and disclosure.
Evidence against
- No network request or command execution is present; the attacker URL is only printed.
Behavioral surface
Filesystem
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node preinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg6"scripts": {
"preinstall": "node preinstall.js"
}
High
Suspicious Lifecycle Evidence
The preinstall hook automatically runs preinstall.js during npm installation.
package.jsonView on unpkg · L6•scripts.preinstall = node preinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpreinstall.js#virtual:normalized:round1View file
Findings
6 High1 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedpreinstall.js#virtual:normalized:round1
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencepreinstall.js
HighAi Review Evidencepreinstall.js
HighAi Review Evidencepreinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to arabsecconf@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing arabsecconf@1.0.0. 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.