registry / Credential exfiltration / flavor-code
flavor-code
<p align="center"><a href="./README.md">English</a> | <b><a href="./README.zh-CN.md">简体中文</a></b></p>
This report shows the evidence for flavor-code@1.3.20. 4 of 28 known versions are blocked or flagged. The newest version, 1.4.3, is allowed. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package deliberately seeds an unauthenticated workspace with a fixed private HTTP OAuth authority and automatically uses it later. Although it is not install-time behavior, this is a concrete credential-exposure path.
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 runs flavor init and subsequently starts the configured client without a cached token.
Impact
A host controlling that address can receive OAuth authorization material and issue or capture session tokens.
Mechanism
Seeded OAuth credential capture through a fixed HTTP endpoint.
Attack narrative
The package's explicit initialization writes a project configuration containing a fixed OAuth server at 192.168.1.100 over plain HTTP. On later startup, the configured provider automatically begins PKCE authentication when no cached token exists, opens the authorization URL, and posts the returned code plus verifier to that host. This makes the generated configuration a credential-capture path rather than a neutral example.
AI rationale
The package deliberately seeds an unauthenticated workspace with a fixed private HTTP OAuth authority and automatically uses it later. Although it is not install-time behavior, this is a concrete credential-exposure path.
Evidence
dist/chunk-Z62P4LL7.js.flavor/flavor.json
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 explicit init command writes a provider configuration pointing OAuth authorization and token requests to a fixed private-network HTTP host.
- At runtime, configured OAuth providers automatically start the PKCE flow when no cached token exists.
- The token exchange sends the authorization code and PKCE verifier to that HTTP endpoint.
Evidence against
- The manifest has no preinstall, install, or postinstall lifecycle hook.
- The project-file mutation is reached through the explicit flavor init command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
17 flagged · loading sourcedist/cli-main.jsView file
56// src/update/apply.ts
L57: import { spawn } from "child_process";
L58: function npmExecutable(platform = process.platform) {
High
dist/desktop/main.jsView file
7402}
L7403: if (["powershell", "pwsh"].includes(name)) {
L7404: const flag = args.findIndex((arg) => ["-command", "-c"].includes(arg.toLowerCase()));
High
8880function runShellHandler(descriptor, event, signal) {
L8881: return new Promise((resolve42, reject) => {
L8882: const env = { ...process.env, ...descriptor.env };
L8883: const invocation = prepareSpawnInvocation(descriptor.command, descriptor.args ?? [], { env });
L8884: const child = spawn(invocation.command, invocation.args, {
L8885: env,
High
Same File Env Network Execution
Findings
1 Critical11 High6 Medium7 Low
CriticalPrevious Version Dangerous Deltadist/chunk-Z62P4LL7.js
HighChild Processdist/cli-main.js
HighShelldist/desktop/main.js
HighSame File Env Network Executiondist/desktop/main.js
HighCredential Redirect Persistencedist/desktop/main.js
HighCommand Output Exfiltrationdist/desktop/main.js
HighCross File Remote Execution Contextdist/cli.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-Z62P4LL7.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to flavor-code@1.3.20.
The versions list below shows the verdict for each recorded version.
- Avoid installing flavor-code@1.3.20. 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.