registry / iflow-engine-base / 4.1.7
iflow-engine-base@4.1.7
⚠ Under reviewBIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected source shows an explicit model-encoding feature and no independently confirmed attack. The required clean citation set is larger than the permitted citation capacity, so this package needs manual review rather than a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Calling the exported model-encoding feature’s start method.
Impact
The selected model properties are disclosed to the configured DeepSeek endpoint as part of encoding.
Mechanism
The method selects model elements and sends their properties to the chat API with a bearer API key.
AI rationale
The inspected source shows an explicit model-encoding feature and no independently confirmed attack. The required clean citation set is larger than the permitted citation capacity, so this package needs manual review rather than a clean verdict.
Evidence
dist/chunks/engine-3d-BA7GiZOL.jsdist/index.d.ts
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
- The manifest points to library entrypoints and lists build and development scripts.
- The exported encoding feature has a public start method that selects model elements for encoding.
- The feature sends model data to the DeepSeek chat API using an API key, but this source alone does not establish malicious behavior.
- The required clean citation set exceeds the 256-citation limit, so clean status cannot be verified under the review requirements.
Evidence against
- The inspected API is a named model-encoding feature with a caller-supplied API-key parameter and an explicit start method.
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/engine-3d-BA7GiZOL.jsView file
14213contains 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/engine-3d-BA7GiZOL.jsView on unpkg · L14213Findings
2 Critical2 High4 Medium6 Low
CriticalTrojan Source Unicodedist/chunks/engine-3d-BA7GiZOL.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.7.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.7 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.