chai-logger
This report shows the evidence for chai-logger@3.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.
OpenSSF/OSV Malicious Advisory
imported 1mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-16380 confirms this npm version as malicious.
Advisory
MAL-2026-16380
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in chai-logger (npm)
Details
The package presents itself as a Chai logging plugin but its main entry `index.js` requires `./lib/query.js`, a ~4 MB obfuscator.io-encoded module (23,868-entry rotated string array, T/j decoder wrappers, hex-property indirection) that executes at the top level as soon as the package is required. The remaining files under `lib/` (proto.js, levels.js, tools.js, etc.) are verbatim copies of pino source, unrelated to the advertised Chai plugin API — a cover story around the obfuscated blob. `package.json` declares `axios ^1.10.0` as a runtime dependency, and the only reference to axios in the shipped code is inside the obfuscated body of `lib/query.js`, giving the payload an HTTP client whose destination is reconstructed at runtime from the rotated string array. Author metadata points to `jsonspack.com`, unrelated to Chai or pino. The combination of import-time execution of a heavily obfuscated payload, a mismatched cover story, copied third-party source used as filler, and an HTTP client declared only for use inside the obfuscated code is the canonical npm credential/data-stealer shape.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package exposes concealed import-time process and network-capable behavior unrelated to its middleware export. No install lifecycle hook or confirmed malicious sink was found, so blocking is not justified.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer imports the package main entrypoint.
Impact
No confirmed attack was established, but hidden command execution and potential network behavior run during import and create unresolved risk.
Mechanism
index.js requires lib/query.js; that payload executes top-level setup and includes an obfuscated execSync fallback.
AI rationale
The package exposes concealed import-time process and network-capable behavior unrelated to its middleware export. No install lifecycle hook or confirmed malicious sink was found, so blocking is not justified.
Evidence
lib/query.js
Independent scan evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for AI warning decision
- The declared main entrypoint imports lib/query.js during package import.
- lib/query.js is a 4 MB single-line obfuscated payload that loads OS, filesystem, and child-process capabilities at top level.
- The obfuscated payload contains a fallback execSync invocation and also loads axios and crypto, preventing a safe determination of its command and network behavior.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The exported middleware only calls next() after imports complete.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVars
HighEntropyStringsMinifiedUrlStrings
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
2L3: const path = require('path');
L4: const { spawn } = require('child_process');
Medium
lib/query.jsView file
1function mc(F,S,Y,E,i){const F9={F:0x1f1};return T(Y-F9.F,E);}function mk(F,S,Y,E,i){const FM={F:0x3dc};return T(i- -FM.F,F);}function ma(F,S,Y,E,i){const Fu={F:0x109};return j(i-F...
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/query.jsView on unpkg · L11Trigger-reachable chain: manifest.main -> index.js -> lib/query.js
L1: function mc(F,S,Y,E,i){const F9={F:0x1f1};return T(Y-F9.F,E);}function mk(F,S,Y,E,i){const FM={F:0x3dc};return T(i- -FM.F,F);}function ma(F,S,Y,E,i){const Fu={F:0x109};return j(i-F...
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
lib/query.jsView on unpkg · L1•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/query.jsView on unpkglib/tools.jsView file
•matchType = malicious_source_fingerprint_signature
signature = 918a45c5f0e59df5
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = chai-as-crack@7.0.5
matchedPath = lib/tools.js
matchedIdentity = npm:Y2hhaS1hcy1jcmFjaw:7.0.5
similarity = 1.000
shingleOverlap = 12
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/tools.jsView on unpkgpackage.jsonView file
5"main": "index.js",
"scripts": {
"smoke:pino": "node ./index.js",
"smoke:file": "node ./file.js"
High
Ai Review Evidence
The declared main entrypoint imports lib/query.js during package import.
package.jsonView on unpkg · L5Findings
2 Critical4 High3 Medium3 Low
CriticalDownload Executelib/query.js
CriticalTrigger Reachable Dangerous Capabilitylib/query.js
HighChild Processindex.js
HighSemantic Analysis Limitedlib/query.js
HighKnown Malware Source Fingerprint Signaturelib/tools.js
HighAi Review Evidencepackage.json
MediumDynamic Requireindex.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to chai-logger@3.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-logger@3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.