registry / Credential exfiltration / @evial/runtime-health
@evial/runtime-health
Lodash-based runtime utility helpers with a small self-registration bootstrap.
This report shows the evidence for @evial/runtime-health@1.0.1, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete, unconsented install-time credential-harvesting and internal-reconnaissance chain, not package-aligned runtime health behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install
Impact
Exposure of local credentials and environment data; access or discovery of cloud and internal services.
Mechanism
install-time credential harvesting, internal reconnaissance, and authenticated MCP probing
Attack narrative
During npm install, postinstall requires scripts/lodash.js. Code appended after the Lodash bundle collects identity, network, and environment data; reads credential files; queries cloud metadata including role credentials; probes internal MCP endpoints with a bearer token taken from environment variables; scans internal ports; and writes the collected data to probe logs.
AI rationale
This is a concrete, unconsented install-time credential-harvesting and internal-reconnaissance chain, not package-aligned runtime health behavior.
Evidence
package.jsonscripts/lodash.jsrt2-probe.logsysinfo2.log/workspace/rt2-probe.log/workspace/sysinfo2.log
Network endpoints5
169.254.169.254100.100.100.200metadata.tencentyun.com10.100.0.4610.201.0.1
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- postinstall directly requires the payload file.
- Payload executes shell commands to collect identity, network, and environment data.
- Payload reads cloud, npm, Kubernetes, Docker, and Git credential files.
- Payload queries cloud metadata and role credential endpoints.
- Payload forwards environment-derived bearer credentials to an internal MCP host.
- Payload scans internal hosts and writes collected output.
Evidence against
- Most of scripts/lodash.js is Lodash 4.17.21, but an executable payload is appended after it.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "require('./scripts/lodash.js')"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "require('./scripts/lodash.js')"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"scripts": {
"postinstall": "node -e \"require('./scripts/lodash.js')\""
High
Suspicious Lifecycle Evidence
postinstall directly requires the payload file.
package.jsonView on unpkg · L7scripts/lodash.jsView file
Findings
1 Critical4 High3 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighCloud Metadata Accessscripts/lodash.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencescripts/lodash.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @evial/runtime-health@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @evial/runtime-health@1.0.1. 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.