iflow-engine-base@4.1.14
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe external request appears to support the SDK’s AI-assisted model encoding and is reached through a public method, so the source does not establish malicious exfiltration. However, a reusable DeepSeek key is embedded in the client bundle and its prefix is logged, creating a concrete key-abuse risk.
Decision evidence
public snapshot- The SDK bundle embeds a DeepSeek API key and logs its prefix during OneClickEncoding construction.
- The public startChat(url, str) method sends its input to DeepSeek’s chat completions endpoint using the embedded key.
- A zero-width character is embedded in the repeated extended property identifier, making the source harder to inspect.
- The package describes itself as a BIM engine SDK and has no lifecycle scripts; the flagged declaration file is API typing.
- The DeepSeek request is reached through the SDK’s explicit startChat method, consistent with its AI-assisted model-encoding feature.
Source & flagged code
7 flaggedPackage source references a known benign dynamic code generation pattern.
distGaussian/gaussian.umd.jsView on unpkg · L1Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/chunks/EngineKernel-CGMWSboO.jsView on unpkg · L7378Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.14.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.14 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.