wrong-notebook@2026.10.26
错题本：上传题目图片，由 AI 识别、解析并标注知识点，支持练习、统计与打印导出
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package automatically uses a linked MiniMax Code account token to claim daily credits while the server runs, and the feature is enabled by default. Although the UI describes the behavior and offers a toggle, the default still performs account actions without a separate user request.
Static reason
One or more suspicious static signals were detected.
Trigger
Starting the server starts the scheduler; it checks after one minute and then periodically while the service remains running.
Impact
The package performs an account action using the user’s token without requiring a separate request for each claim.
Mechanism
Unless auto-check-in is disabled, the code uses the saved MiniMax account token to check sign-in status and POST a claim when today is not checked in.
Attack narrative
Starting the server activates a periodic MiniMax Code check-in scheduler. Because auto-check-in defaults to enabled, it uses the saved account token to check the daily status and POST a claim when needed. The settings UI discloses the feature, but it is enabled by default and performs account actions without a separate request for each claim.
AI rationale
The package automatically uses a linked MiniMax Code account token to claim daily credits while the server runs, and the feature is enabled by default. Although the UI describes the behavior and offers a toggle, the default still performs account actions without a separate user request.
Evidence
.next/server/chunks/src_03_og0nynnyx2._.js.next/server/chunks/src_lib_05svhzm9a162-._.js.next/server/chunks/src_lib_minimax-code_checkin_ts_1j1mpuxc1vgoz._.js.next/server/chunks/ssr/_00np6xqvkg6u-._.jsconfig/minimax-code.json
Network endpoints2
account.minimax.cnagent.minimax.cn
Decision evidence
public snapshotAI called this Malicious at 93.0% confidence as Malware with low false-positive risk.
Evidence for block
- Server startup registers a MiniMax Code check-in scheduler that runs after a delay and periodically while the service is running.
- MiniMax Code auto-check-in defaults to enabled unless the environment explicitly sets MINIMAX_CODE_AUTO_CHECKIN to false.
- The check-in flow uses a bearer token for MiniMax requests and sends a POST to claim daily sign-in credits.
- The app checks whether today’s check-in is already complete before attempting a claim.
- The settings UI describes the feature as daily auto check-in that collects MiniMax Code credits while the service runs.
- The package’s install hook invokes Prisma client generation.
Evidence against
- The auto-check-in behavior is described in the settings UI and has a configuration toggle, though it is enabled by default.
- The install hook runs Prisma client generation, consistent with the package’s database setup.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
6 flaggedpackage.jsonView file
•scripts registry_only=start
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg•scripts.postinstall = node bin/wrong-notebook.js prepare-client
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/wrong-notebook.js prepare-client
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg.next/server/chunks/ssr/_00np6xqvkg6u-._.jsView file
Findings
1 Critical1 High7 Medium3 Low
CriticalManifest Confusionpackage.json
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Pattern.next/server/chunks/ssr/_00np6xqvkg6u-._.js
MediumDynamic Requirebin/wrong-notebook.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSecret Pattern.next/static/chunks/2ods71pgjc-e2.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to wrong-notebook@2026.10.26.
See all versions of wrong-notebook for other recorded verdicts.
- Avoid installing wrong-notebook@2026.10.26. 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.