registry / Remote code execution / chai-as-relay
chai-as-relay
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-as-relay@1.2.1, the only known version.
This package appears in our research on the fake chai plugin campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe published main module immediately runs an obfuscated payload that loads shell execution, filesystem access, and an HTTP client. That is hidden import-time attack behavior, not a logger feature.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Node loads index.js through the package main entry, which requires lib/config.js at import time.
Impact
A consumer that imports the package can have arbitrary local commands and network requests run from the obfuscated payload.
Mechanism
The required file is an immediately executing obfuscated script that acquires shell execution, filesystem access, and an HTTP client.
Attack narrative
chai-as-relay 1.2.1 presents a logger-style entry, but index.js requires lib/config.js on load. That file is a multi-megabyte obfuscated script. During execution it requires os, fs, child_process execSync and spawn, axios, and crypto. No install hook is needed: importing the published main module is enough to run the hidden loader. Command strings and destinations stay encoded, so the concrete effect is untrusted code execution and outbound access from the importer process.
AI rationale
The published main module immediately runs an obfuscated payload that loads shell execution, filesystem access, and an HTTP client. That is hidden import-time attack behavior, not a logger feature.
Evidence
package.jsonindex.jslib/config.js
Decision evidence
public snapshotAI called this Malicious at 92.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json sets main to index.js for chai-as-relay 1.2.1 and defines only smoke scripts, with no install lifecycle hooks.
- index.js loads child_process and requires ./lib/config as soon as the module is imported.
- lib/config.js is a single-line obfuscated function that executes when that module is loaded.
- Inside that payload the code requires os, fs, and child_process execSync plus spawn.
- The same payload also requires axios and the crypto module.
Evidence against
- No preinstall, install, or postinstall script is declared in package.json.
- The exported middleware function only calls next and does not itself send data.
Behavioral surface
ChildProcessEnvironmentVars
HighEntropyStringsMinifiedUrlStrings
Oversized source lightweight scan
Source & flagged code
7 flagged · loading sourceindex.jsView file
3const path = require('path');
L4: const { spawn } = require('child_process');
L5: const { DEFAULT_LEVELS, SORTING_ORDER } = require('./lib/constants');
High
3const path = require('path');
const { spawn } = require('child_process');
const { DEFAULT_LEVELS, SORTING_ORDER } = require('./lib/constants');
const config
High
Ai Review Evidence
index.js loads child_process and requires ./lib/config as soon as the module is imported.
index.jsView on unpkg · L3lib/config.jsView file
1(function(z,w){const FZ={z:0xec3,w:0x3ac1,f:0x149,S:0x1f2b,C:0x3960,y:0x3dc9,l:0x4f51,a:0x628f,k:0x64de,o:0x73cb,M:0x34a2,W:0x37af,V:0x590b,L:0x33cd,O:0x29c9,I:0x4604,c:0x2651,E:'\...
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/config.jsView on unpkg · L1Findings
2 Critical4 High3 Medium3 Low
CriticalDownload Executelib/config.js
CriticalTrigger Reachable Dangerous Capabilitylib/config.js
HighChild Processindex.js
HighSemantic Analysis Limitedlib/config.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceindex.js
MediumEnvironment Vars
MediumOversized Source Filelib/config.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to chai-as-relay@1.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-as-relay@1.2.1. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.