@zoryn/component
Vue 3 + TypeScript 企业级组件库(pnpm monorepo)。对外主包 `@zoryn/component`,组件 `Z` 前缀,支持完整导入与按需导入。
This report shows the evidence for @zoryn/component@1.1.17. 1 of 4 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe preview automatically sends spreadsheet cell content and internal diagnostics to a fixed localhost endpoint without disclosure or consent. This hidden collection supports a malicious data-exfiltration verdict.
Decision evidence
public snapshot- The grid import preview sends the first spreadsheet cell to a hard-coded localhost debug endpoint in a POST request.
- The same endpoint receives spreadsheet style and rendering diagnostics in additional POST requests.
- The preview calls the data-writing function automatically when mounted, triggering these requests without a separate user action.
- The behavior is in the grid import preview component, rather than being triggered by importing the package generally.
- The reported Unicode pattern in the minified bundle is an escaped CodeMirror special-character regex.
Source & flagged code
5 flaggedPackage source references a known benign dynamic code generation pattern.
lib/components/form-designer/src/designer/components/FnEditor.jsView on unpkg · L85Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/index.full.min.jsView on unpkg · L183Findings
Affected versions and remediation
This report applies to @zoryn/component@1.1.17.
The versions list below shows the verdict for each recorded version.
- Avoid installing @zoryn/component@1.1.17. 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.