registry / Data exfiltration / chai-as-stringify

chai-as-stringify

This document describes the management of vulnerabilities for the project and all modules within the organization.

This report shows the evidence for chai-as-stringify@7.0.2, 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 3mo ago · by lpm-firewall-ai

This is unrelated to the declared middleware behavior and executes without user invocation beyond importing the package. Obfuscation, host collection, outbound transmission, and command execution establish malicious behavior.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

Require/import of index.js or any consumer that loads the package.

Impact

Host/user metadata exposure and arbitrary shell-command execution in the importing process.

Mechanism

Obfuscated import-time host reconnaissance, command execution, and HTTP exfiltration.

Attack narrative

The main entrypoint imports lib/config.js during package load. That file immediately executes a heavily obfuscated payload which imports filesystem, OS, process-execution, HTTP, and crypto facilities; constructs host, OS, and username fields; and sends them via axios. It also contains execSync and spawn paths, including a fallback that installs missing dependencies. The destination is runtime-obfuscated, but the import-time collection and outbound request mechanism are concrete.

AI rationale

Evidence

package.jsonindex.jslib/config.js

Decision evidence

public snapshot

AI called this Malicious at 98.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json loads index.js with no lifecycle hook.
index.js imports ./lib/config at module load.
lib/config.js is a 4 MB obfuscated import-time payload.
lib/config.js loads fs, os, child_process execSync/spawn, axios, and crypto.
lib/config.js builds host, OS, and username data then sends it with axios.
lib/config.js contains multiple execSync paths, including a dependency-install fallback.

Evidence against

index.js exports a no-op Express-style middleware.
No npm preinstall, install, or postinstall hook is declared.

Behavioral surface

Source

ChildProcessEnvironmentVars

Supply chain

HighEntropyStringsMinifiedUrlStrings

ManifestNo manifest risk signals triggered.

scanned 15 file(s), 307 KB of source, external domains: github.com

Oversized source lightweight scan

lib/config.js

Source & flagged code

4 flagged

index.jsView file

3const path = require('path'); L4: const { spawn } = require('child_process'); L5: const { DEFAULT_LEVELS, SORTING_ORDER } = require('./lib/constants');

High

Child Process

Package source references child process execution.

index.jsView on unpkg · L3

lib/config.jsView file

1function mw(F,S,Y,E,i){const TL={F:0xc3};return j(Y- -TL.F,E);}(function(F,S){const TZ={F:0x7425,S:0x30ac,Y:'\x6a\x24\x30\x42',E:0x34b9,i:0x5616,B:0x4577,N:0x40ad,V:'\x35\x6b\x76\x...

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/config.jsView on unpkg · L1

1Trigger-reachable chain: manifest.main -> index.js -> lib/config.js L1: function mw(F,S,Y,E,i){const TL={F:0xc3};return j(Y- -TL.F,E);}(function(F,S){const TZ={F:0x7425,S:0x30ac,Y:'\x6a\x24\x30\x42',E:0x34b9,i:0x5616,B:0x4577,N:0x40ad,V:'\x35\x6b\x76\x...

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

lib/config.jsView on unpkg · L1

docs/transports.mdView file

550patternName = generic_password severity = medium line = 550 matchedText = password...rd',

Medium

Secret Pattern

Hardcoded password in docs/transports.md

docs/transports.mdView on unpkg · L550

Source & flagged code

4 flagged · loading source

index.jsView file

3const path = require('path'); L4: const { spawn } = require('child_process'); L5: const { DEFAULT_LEVELS, SORTING_ORDER } = require('./lib/constants');

High

Child Process

Package source references child process execution.

index.jsView on unpkg · L3

lib/config.jsView file

1function mw(F,S,Y,E,i){const TL={F:0xc3};return j(Y- -TL.F,E);}(function(F,S){const TZ={F:0x7425,S:0x30ac,Y:'\x6a\x24\x30\x42',E:0x34b9,i:0x5616,B:0x4577,N:0x40ad,V:'\x35\x6b\x76\x...

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/config.jsView on unpkg · L1

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

Findings

2 Critical1 High3 Medium3 Low

CriticalDownload Executelib/config.js

CriticalTrigger Reachable Dangerous Capabilitylib/config.js

HighChild Processindex.js

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

MediumSecret Patterndocs/transports.md

LowScripts Present

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to chai-as-stringify@7.0.2.

The versions list below shows the verdict for each recorded version.

Avoid installing chai-as-stringify@7.0.2. 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: 2026-07-22 14:48:47.044Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

7.0.2latestshownMaliciousData ExfiltrationBlockPublishedJul 22, 2026, 1:55 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Behavioral surface

Related packages

Other data exfiltration packages

Source & flagged code