registry / iflow-engine-base / 4.1.12
iflow-engine-base@4.1.12
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis BIM SDK’s inspected external request is triggered by its one-click encoding operation and sends selected model properties to the DeepSeek endpoint for encoding. No install-time or import-time attack behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A caller invokes oneClickEncoding.start().
Impact
Selected BIM property data leaves the application for the encoding request; no automatic collection or unrelated credential transmission was identified.
Mechanism
The feature queries selected component properties, batches them, sends them to api.deepseek.com using its configured API key, and saves generated results in browser localStorage.
AI rationale
This BIM SDK’s inspected external request is triggered by its one-click encoding operation and sends selected model properties to the DeepSeek endpoint for encoding. No install-time or import-time attack behavior was identified.
Network endpoints1
api.deepseek.com/v1/chat/completions
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a BIM Engine SDK and has no install lifecycle hooks.
- The DeepSeek request is part of the exposed one-click encoding feature, which has an explicit start() method.
- The feature queries BIM component properties, batches the results, and passes them to the chat request.
- The request goes to api.deepseek.com and uses the feature’s configured API key.
Evidence against
- The feature stores generated encoding results in browser localStorage.
- A zero-width character appears in an internal property identifier, but the inspected code uses it consistently and it does not conceal an attack flow.
Behavioral surface
CryptoEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
7 flaggeddistGaussian/gaussian.umd.jsView file
1(function(rt,St){typeof exports=="object"&&typeof module<"u"?St(exports,require("three"),require("@mkkellogg/gaussian-splats-3d")):typeof define=="function"&&define.amd?define(["ex...
L2: \0`,ie+=g(Q,2),ie+=C.magic,ie+=g(m,2),ie+=g(_,2),ie+=g(oe.crc32,4),ie+=g(oe.compressedSize,4),ie+=g(oe.uncompressedSize,4),ie+=g(i.length,2),ie+=g(H.length,2),{fileRecord:T.LOCAL_F...
L3: `)}return u},a.decode=function(d,x){if(typeof d!="string")throw new TypeError('"input" must be a string.');if(typeof x!="string")throw new TypeError('"alphabet" must be a string.')...
Low
Eval
Package source references a known benign dynamic code generation pattern.
distGaussian/gaussian.umd.jsView on unpkg · L1dist/chunks/EngineKernel-TcLcfKF2.jsView file
7377contains invisible/control Unicode U+200C (zero width non-joiner)
extended<U+200C> = /* @__PURE__ */ new Map();
Critical
Trojan Source Unicode
Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/chunks/EngineKernel-TcLcfKF2.jsView on unpkg · L7377Findings
2 Critical2 High4 Medium6 Low
CriticalTrojan Source Unicodedist/chunks/EngineKernel-TcLcfKF2.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.d.ts
HighShips High Entropy Blobdist/assets/hdr/17.hdr
HighSemantic Analysis Limiteddist/bim-engine-sdk.umd.js
MediumNetwork
MediumShips Wasm Moduledist/draco/draco_decoder.wasm
MediumOversized Source Filedist/bim-engine-sdk.umd.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldistGaussian/gaussian.umd.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.12.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.12 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.