registry / iflow-engine-base / 4.1.5
iflow-engine-base@4.1.5
⚠ Under reviewBIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected transfer matches the SDK's AI-assisted encoding feature and is activated through its start method. A clean verdict could not be supported within the required citation limit for the complete coverage set, and that limitation alone does not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Calling the engine's one-click encoding start method activates the feature.
Impact
Model properties are sent to an external AI service for encoding; the inspected behavior does not establish credential theft or malicious intent.
Mechanism
The feature gathers selected model properties and posts them as a chat request using a built-in default API key.
AI rationale
The inspected transfer matches the SDK's AI-assisted encoding feature and is activated through its start method. A clean verdict could not be supported within the required citation limit for the complete coverage set, and that limitation alone does not establish malicious behavior.
Evidence
dist/chunks/EngineKernel-DQbK_INv.js
Network endpoints1
api.deepseek.com
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json identifies this as a BIM engine SDK and points its main entry to the bundled engine.
- The engine constructs a one-click encoding feature as part of engine initialization.
- The encoding method gathers model element properties and sends them to the DeepSeek chat API with a built-in default API key.
Evidence against
- The inspected transfer is tied to the SDK's model-encoding feature; no separate credential theft or install-time attack was established.
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-DQbK_INv.jsView file
7320contains 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-DQbK_INv.jsView on unpkg · L7320Findings
2 Critical2 High4 Medium6 Low
CriticalTrojan Source Unicodedist/chunks/EngineKernel-DQbK_INv.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.5.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.5 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.