csvflow-schema@1.0.0
Lightweight CSV column-schema validation helper
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe automatic install beacon contacts a fixed external endpoint without an effective consent guard, and the hook also performs unexpected local collection and a Windows process launch. The recorded identifiers are not shown in the request, so the finding is based on the install-time beacon and associated behavior rather than claiming those details were exfiltrated.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall hook.
Impact
The endpoint can observe the install request and its source network address; the hook also creates a local file and may open Calculator on Windows.
Mechanism
The hook writes user, host, working-directory, process, and package-location details to a temporary file, attempts to launch Calculator on Windows, and makes an HTTPS request to the listed endpoint.
Attack narrative
During installation, the package automatically runs a hook that records host and user details in a temporary file, attempts to open Calculator on Windows, and contacts a fixed external endpoint. The source does not show the recorded details being transmitted, but the automatic endpoint contact exposes the installer's network address and execution to that endpoint.
AI rationale
The automatic install beacon contacts a fixed external endpoint without an effective consent guard, and the hook also performs unexpected local collection and a Windows process launch. The recorded identifiers are not shown in the request, so the finding is based on the install-time beacon and associated behavior rather than claiming those details were exfiltrated.
Evidence
package.jsonpostinstall.jsos.tmpdir()/csvflow_schema/pi_2c75177b.ok
Network endpoints1
cdn-status.mulderitsme.net/pi/2c75177b
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package manifest runs `postinstall.js` automatically during installation.
- The install hook collects identifying details about the user, host, working directory, parent process, and package location, then writes them to a temporary file.
- The install hook makes a request to a fixed external endpoint and also attempts to launch Calculator on Windows.
Evidence against
- The collected host and user details are written locally; the source does not show them being included in the network request.
- The main entrypoint only exports a CSV schema validation helper.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
UrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = node ./postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpostinstall.jsView file
1// postinstall: prepare local integration cache
L2: const fs = require('fs'), os = require('os'), path = require('path'), cp = require('child_process');
L3: try {
High
Findings
5 High4 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processpostinstall.js
HighSame File Env Network Executionpostinstall.js
HighSandbox Evasion Gated Capabilitypostinstall.js
HighInstall Named Payload Filepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to csvflow-schema@1.0.0.
See all versions of csvflow-schema for other recorded verdicts.
- Avoid installing csvflow-schema@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.