registry / Data exfiltration / zystcdemo
zystcdemo
A simple date formatting utility
This report shows the evidence for zystcdemo@1.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe automatic install hook silently sends the installing user's account name and machine details to a remote server unrelated to the package's stated date-formatting purpose. This is concrete install-time data exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
Automatically during npm install through the postinstall lifecycle script.
Impact
Discloses the installing user's account name and machine details to the endpoint.
Mechanism
Runs whoami, reads the hostname and platform, adds a timestamp, then POSTs the JSON data to the configured endpoint.
Attack narrative
During installation, the postinstall hook executes whoami, collects the machine hostname and platform, and POSTs these details with a timestamp to a remote endpoint. The code suppresses failures so installation continues quietly. The package's ordinary date formatter does not require this collection or transmission.
AI rationale
The automatic install hook silently sends the installing user's account name and machine details to a remote server unrelated to the package's stated date-formatting purpose. This is concrete install-time data exfiltration.
Evidence
package.jsonpostinstall.jsindex.js
Network endpoints2
srctest.zystcc.cn/collectPOC_SERVER (environment-configurable endpoint)
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 automatically during installation.
- postinstall.js executes whoami and collects the result, hostname, platform, and timestamp.
- The collected data is sent in an HTTP POST to https://srctest.zystcc.cn/collect, with the server configurable through POC_SERVER.
- The reporting function is called automatically and silently ignores failures.
- index.js exports a date formatter; its comment says the package is made to look like an ordinary date utility.
Evidence against
- The package has a date formatting utility as its main export.
- The payload does not include credentials in the inspected source.
Behavioral surface
ChildProcessEnvironmentVarsNetworkShell
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 unpkg6"scripts": {
"postinstall": "node postinstall.js"
},
"keywords": [
"date",
High
Suspicious Lifecycle Evidence
package.json runs postinstall.js automatically during installation.
package.jsonView on unpkg · L6•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
Findings
6 High4 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processpostinstall.js
HighShell
HighSame File Env Network Executionpostinstall.js
HighSandbox Evasion Gated Capabilitypostinstall.js
HighSuspicious Lifecycle Evidencepackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to zystcdemo@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing zystcdemo@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.