@mexc/shared-utils
dios confirming for bugrap and mexc that this namespace is taken
This report shows the evidence for @mexc/shared-utils@2.0.0. 2 of 5 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package has an unconsented postinstall that collects system/user data and mutates the filesystem, explicitly presented as dependency-confusion proof behavior. No exfiltration endpoint is needed to establish the malicious install-time action.
Decision evidence
public snapshot- package.json runs postinstall via node postinstall.js.
- postinstall.js collects hostname, username, cwd, platform, Node version, and temp directory.
- postinstall.js writes collected host metadata to a predictable temp file on install.
- Source describes a dependency-confusion takeover/confirmation.
- No network or credential exfiltration is present.
- index.js contains only stub utility functions.
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @mexc/shared-utils@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @mexc/shared-utils@2.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.