nixamp@0.62.3
It really whips the terminal's ass. A Winamp-shaped audio player for your terminal.
AI Security Review
scanned 2d ago · by lpm-firewall-aiSource inspection confirms an automatic, authenticated account change that is not gated by the user's publish choice. The directory is package-configured, and the code itself describes the action as occurring without being asked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Starting the server with a session token and a publishable address.
Impact
The directory account is changed and receives the server details without a specific confirmation for this action.
Mechanism
The server sends an authenticated POST with the machine's address, name, and key; this request is separate from the publish-setting check.
Attack narrative
On server startup, if a saved session token and publishable address are present, the package posts the machine's address, name, and key to the Nixamp directory using the token. This account mutation is separate from the publish-setting check, so it can occur even when publishing is disabled.
AI rationale
Source inspection confirms an automatic, authenticated account change that is not gated by the user's publish choice. The directory is package-configured, and the code itself describes the action as occurring without being asked.
Evidence
dist/server.jsdist/directory.js
Network endpoints1
nixamp.com/api/v1/servers
Decision evidence
public snapshotAI called this Malicious at 84.0% confidence as Malware with low false-positive risk.
Evidence for block
- When a signed-in server has a publishable address, startup posts to the directory with the session token and server details.
- The code describes this account change as happening without being asked; the request is not gated by the separate publish setting.
Evidence against
- The destination is the package's configured Nixamp directory, and the code says a prior manual command performed the same account action.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
8 flagged · loading sourcedist/links.jsView file
22import { createHash } from "node:crypto";
L23: import { spawn } from "node:child_process";
L24: import { parseCatalog } from "./catalogs.js";
High
dist/speech.jsView file
230try {
L231: return (await import(__rewriteRelativeImportExtension(name)));
L232: }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/speech.jsView on unpkg · L230dist/catalogs.jsView file
127* decorates the URL on the next line, `#EXTGRP:News` names the group for
L128: * lists that write it that way instead, and `#EXTIMG:https://...` is the
L129: * picture for lists (a podcast's episodes, say) that carry one that way
...
L209: throw new Error(`${source} answered ${answer.status}`);
L210: const text = await answer.text();
L211: if (text.length > maxBytes)
Findings
1 Critical4 High5 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationweb/dist/assets/radio-DmVc3wpH.js
HighChild Processdist/links.js
HighCommand Output Exfiltrationdist/server.js
HighSandbox Evasion Gated Capabilitydist/manage.js
HighSemantic Analysis Limiteddist/accounts.js#virtual:string-array:round1
MediumDynamic Requiredist/speech.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperweb/dist/install.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowWeak Cryptodist/catalogs.js
Low
Affected versions and remediation
This report applies to nixamp@0.62.3.
See all versions of nixamp for other recorded verdicts.
- Avoid installing nixamp@0.62.3. 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.