@pisell/pisellos@2.2.317
一个可扩展的前端模块化SDK框架，支持插件系统
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source establishes an active runtime transfer of application log records to a publisher-selected default webhook. Caller configuration can override the destination, but leaving the default in place still sends those records.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer initializes ScanOrder without replacing its logger configuration, then invokes logged ScanOrder operations.
Impact
Application records and identifying host or cache context are disclosed to the webhook recipient.
Mechanism
The logger builds records from operation data and posts their serialized contents to the default webhook.
Attack narrative
On initialization, ScanOrder chooses Feishu by default and supplies a fixed webhook unless the consumer overrides its logger configuration. Calls to logged operations produce records containing operation payloads and context, which the Feishu provider serializes and sends in a POST request. This exposes consumer application data to the package-selected recipient without an affirmative send-consent check.
AI rationale
The source establishes an active runtime transfer of application log records to a publisher-selected default webhook. Caller configuration can override the destination, but leaving the default in place still sends those records.
Evidence
dist/solution/ScanOrder/index.jsdist/modules/ScanOrderLogger/index.jsdist/modules/ScanOrderLogger/providers/feishu.js
Network endpoints1
open.feishu.cn
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- ScanOrder initialization selects Feishu by default and installs a publisher-specified webhook when no logger configuration is supplied.
- ScanOrder methods generate logs during operation calls and forward them to the logger.
- The logger records payloads, extra data, cache context, and the current host.
- The Feishu provider serializes log contents and sends them in a POST request to the configured webhook.
Evidence against
- The logger supports caller-supplied provider configuration, which can replace the default destination.
Behavioral surface
EnvironmentVarsEvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcedist/plugins/window.jsView file
•matchType = normalized_sha256
matchedPackage = @pisell/pisellos@2.3.165
matchedPath = dist/plugins/window.js
matchedIdentity = npm:QHBpc2VsbC9waXNlbGxvcw:2.3.165
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
HighKnown Malware Source Fingerprint Signaturelib/modules/AccountList/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.2.317.
See all versions of @pisell/pisellos for other recorded verdicts.
- Avoid installing @pisell/pisellos@2.2.317. 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.