@pisell/pisellos@2.3.165
一个可扩展的前端模块化SDK框架，支持插件系统
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource confirms automatic runtime log transmission to hardcoded Feishu webhooks, including customer identifiers in log payloads. A configuration override is available, but the default sends data to a publisher-selected recipient without an effective consent gate.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
ScanOrder initialization followed by customer login or other logged activity.
Impact
Customer identifiers and other logged application data may be disclosed to the publisher-selected recipient without recipient-specific consent.
Mechanism
The logger serializes record payloads and POSTs them to the default Feishu webhook unless configuration overrides it.
Attack narrative
When ScanOrder initializes, it defaults to Feishu logging and supplies fixed webhook destinations if no logger configuration is provided. Customer-login activity adds the customer ID to a log record. The Feishu provider serializes record payloads and sends them to the selected webhook, so the default configuration discloses customer and application data without recipient-specific consent.
AI rationale
Source confirms automatic runtime log transmission to hardcoded Feishu webhooks, including customer identifiers in log payloads. A configuration override is available, but the default sends data to a publisher-selected recipient without an effective consent gate.
Evidence
dist/solution/ScanOrder/index.jsdist/modules/ScanOrderLogger/index.jsdist/modules/ScanOrderLogger/providers/feishu.js
Network endpoints2
open.feishu.cn/open-apis/bot/v2/hook/216b3fe6-af98-424e-8706-f0471241a7edopen.feishu.cn/open-apis/bot/v2/hook/015b7c2a-dd3c-4c30-9898-ef0f5253111f
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- ScanOrder selects Feishu logging by default and supplies hardcoded webhook destinations when no logger configuration is provided.
- The customer-login handler adds the customer ID to a log record.
- The Feishu provider includes each record's payload in its message and POSTs the message to the webhook.
- The logger forwards records with its provider configuration, without a recipient-specific consent check.
Evidence against
- The provider and webhook can be overridden through ScanOrder configuration.
- The manifest has a prepublishOnly build hook, not an install-time hook.
Behavioral surface
EnvironmentVarsEvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcedist/plugins/window.jsView file
•matchType = normalized_sha256
matchedPackage = @pisell/pisellos@2.2.316
matchedPath = dist/plugins/window.js
matchedIdentity = npm:QHBpc2VsbC9waXNlbGxvcw:2.2.316
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/plugins/window.jsView on unpkg248} else {
L249: eval(handler);
L250: }
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/plugins/window.jsView on unpkg · L248dist/solution/ScanOrder/index.jsView file
•Default hardcoded logging webhook in dist/solution/ScanOrder/index.js:
this.store.scanOrderLogger.setProviderConfig(((_this$otherParams5 = this.otherParams) === null || _this$otherParams5 === void 0 ? void 0 : _this$otherParams5.scanOrderLoggerConfig)...
webhook: 'https://open.feishu.cn/open-apis/bot/v2/hook/216b3fe6-af98-424e-8706-f0471241a7ed',
errorHook: 'https://open.feishu.cn/open-apis/bot/v2/hook/015b7c2a-dd3c-4c30-9898-ef0f5253111f'
Rich runtime records posted to the webhook in [redacted].js:
var context = record.context || {};
text: "\u65E5\u5FD7\u5185\u5BB9: ".concat(safeStringify(record.payload), "\n")
text: "\u6269\u5C55\u4FE1\u606F: ".concat(safeStringify(record.extra), "\n")
return fetch(webhook, {
Reachable runtime logger calls in dist/modules/Order/index.js:
this.logger.addL
Findings
1 Critical3 High3 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/solution/ScanOrder/index.js
HighSemantic Analysis Limitedlib/solution/RegisterAndLogin/utils.js#virtual:normalized:round1
HighKnown Malware Source Similaritydist/plugins/window.js
HighAi Review Evidencedist/solution/ScanOrder/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvaldist/plugins/window.js
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @pisell/pisellos@2.3.165.
See all versions of @pisell/pisellos for other recorded verdicts.
- Avoid installing @pisell/pisellos@2.3.165. 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.