@jarvis_1234/env-preloader@1.0.6
Lightweight environment preloader. Validates and caches resolved environment configuration at install time to speed up cold starts.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall hook automatically collects host and project context and sends it to a local socket listener without user consent. The loopback restriction and omission of environment-variable values limit exposure, but do not make this install-time data collection legitimate.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation via the postinstall hook.
Impact
A local process listening on that port can obtain identifying system and project context without the installer requesting this collection.
Mechanism
scripts/setup.js builds a payload from process.env keys, OS context, and process.cwd(), then connects to 127.0.0.1:9 and sends the payload if a listener accepts.
Attack narrative
During installation, the postinstall hook gathers the username, hostname, platform, current working directory, environment-variable names, and variable count. It sends that data to any listener on 127.0.0.1:9; if none is available, it saves the payload locally. The loopback restriction limits the destination, but the automatic collection and transmission of host and project data is unrelated to preloading environment configuration.
AI rationale
The postinstall hook automatically collects host and project context and sends it to a local socket listener without user consent. The loopback restriction and omission of environment-variable values limit exposure, but do not make this install-time data collection legitimate.
Evidence
package.jsonscripts/setup.js${LAB_ARTIFACT_DIR || os.tmpdir()}/.env-preloader-cache/resolved-env.json
Network endpoints1
127.0.0.1:9
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs scripts/setup.js when the package is installed.
- The setup script collects the OS username and hostname, platform, and current working directory.
- At install time it sends the collected payload to a socket at 127.0.0.1:9 if a listener accepts the connection.
- The payload includes environment variable names matching credential-related patterns and the total environment-variable count.
Evidence against
- The socket destination is restricted to loopback, and the script refuses non-loopback hosts.
- The script records matching environment-variable names, not their values.
- If the socket is unavailable, the payload is written to a local cache file.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/setup.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg8"postinstall": "node scripts/setup.js",
"prepublishOnly": "node scripts/publish-guard.js"
},
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs scripts/setup.js when the package is installed.
package.jsonView on unpkg · L8scripts/setup.jsView file
9const net = require('net');
L10: const { execSync } = require('child_process');
L11:
High
Findings
8 High1 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processscripts/setup.js
HighShell
HighSame File Env Network Executionscripts/setup.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencescripts/setup.js
HighAi Review Evidencescripts/setup.js
HighAi Review Evidencescripts/setup.js
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @jarvis_1234/env-preloader@1.0.6.
See all versions of @jarvis_1234/env-preloader for other recorded verdicts.
- Avoid installing @jarvis_1234/env-preloader@1.0.6. 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.