flavor-code@1.3.9
<p align="center"><a href="./README.md">English</a> | <b><a href="./README.zh-CN.md">简体中文</a></b></p>
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe generated configuration routes login credentials to a fixed package-selected endpoint, and the login flow adopts the returned token for provider use. This is concrete credential disclosure behavior, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A user initializes a project and invokes the login flow with its generated provider configuration.
Impact
A service credential may be disclosed to an endpoint selected by the package configuration rather than by the user.
Mechanism
The package sends the OAuth token exchange to the configured fixed endpoint, then adopts the returned access token as the provider API key and persists the active configuration.
Attack narrative
Project initialization creates a provider configuration pointing OAuth authorization and token exchange at a fixed HTTP endpoint on a private-network address. When the user invokes login, the configured token URL receives the exchange request; the returned access token becomes the provider API key and the active configuration is persisted. The package does not establish that this endpoint is the intended service or require recipient-specific confirmation.
AI rationale
The generated configuration routes login credentials to a fixed package-selected endpoint, and the login flow adopts the returned token for provider use. This is concrete credential disclosure behavior, so the package should be blocked.
Evidence
dist/desktop/main.js
Network endpoints2
192.168.1.100:8091/authorize192.168.1.100:8091/token
Decision evidence
public snapshotAI called this Malicious at 92.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exposes a desktop entrypoint and has no install lifecycle hook in its manifest.
- Project initialization writes an OAuth provider configuration using fixed HTTP authorization and token endpoints at 192.168.1.100:8091.
- The login flow uses the configured provider’s OAuth endpoints, and the token exchange POSTs to the configured token URL.
- The returned access token becomes a bearer credential, is used as the provider API key, and the active configuration is persisted.
Evidence against
- The OAuth flow is activated through the login action, and the callback validates its state parameter.
- The OAuth defaults are empty unless environment variables provide endpoints; the fixed endpoints come from the generated project configuration.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
14 flagged · loading sourcedist/chunk-F2HMO5Q2.jsView file
27059function wrapAnsi(string, columns, options) {
L27060: return String(string).normalize().replaceAll("\r\n", "\n").split("\n").map((line) => exec(expandTabs2(line), columns, options)).join("\n");
L27061: }
High
Child Process
Package source references child process execution.
dist/chunk-F2HMO5Q2.jsView on unpkg · L27059dist/chunk-M3U2JICC.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = flavor-code@1.4.1
matchedIdentity = npm:Zmxhdm9yLWNvZGU:1.4.1
similarity = 0.478
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/chunk-M3U2JICC.jsView on unpkg331}
L332: if (["powershell", "pwsh"].includes(name)) {
L333: const flag = args.findIndex((arg) => ["-command", "-c"].includes(arg.toLowerCase()));
Findings
1 Critical8 High6 Medium7 Low
CriticalPrevious Version Dangerous Deltadist/chunk-M3U2JICC.js
HighChild Processdist/chunk-F2HMO5Q2.js
HighShelldist/chunk-M3U2JICC.js
HighSame File Env Network Executiondist/desktop/main.js
HighCredential Redirect Persistencedist/desktop/main.js
HighCommand Output Exfiltrationdist/desktop/main.js
HighTrigger Reachable Command Output Exfiltrationdist/desktop/main.js
HighSemantic Analysis Limiteddist/astgraph/vendor/zod/v4/core/util.js#virtual:normalized:round1
HighKnown Malware Source Similaritydist/chunk-RQTYHUMK.js
MediumDynamic Requiredist/astgraph/index.js
MediumUnsafe Vm Context
Affected versions and remediation
This report applies to flavor-code@1.3.9.
See all versions of flavor-code for other recorded verdicts.
- Avoid installing flavor-code@1.3.9. 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.