registry / Remote code execution / chai-as-smart
chai-as-smart
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-as-smart@2.3.5, 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 4mo ago · by lpm-firewall-aiDirect source inspection confirms hidden runtime network execution of server-supplied code from an unrelated endpoint. Absence of install hooks narrows the trigger but does not remove the concrete malicious backdoor.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Runtime use of the exported middleware from index.js.
Impact
Remote endpoint operator can run arbitrary JavaScript with require access in the consuming project runtime.
Mechanism
detached child process plus remote response execution with new Function
Attack narrative
The package main entrypoint exposes middleware that starts lib/initializeCaller.js in a detached background Node process. The helper decodes a hidden HTTPS endpoint, posts data to it, then constructs and runs a function from response.data with require access. That gives the remote server arbitrary code execution when the package is used.
AI rationale
Direct source inspection confirms hidden runtime network execution of server-supplied code from an unrelated endpoint. Absence of install hooks narrows the trigger but does not remove the concrete malicious backdoor.
Evidence
package.jsonindex.jslib/initializeCaller.js
Network endpoints1
ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json sets main to index.js and has no lifecycle scripts.
- index.js imports child_process.spawn and starts node lib/initializeCaller.js detached with stdio ignored.
- index.js exported middleware calls runBackgroundTask on runtime use.
- lib/initializeCaller.js decodes DEV_API_KEY to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df.
- lib/initializeCaller.js posts to that endpoint and executes response.data via new Function("require", response.data).
Evidence against
- No preinstall/install/postinstall hook was present in package.json.
- lib/initializeCaller.js shadows process.env with hardcoded DEV_* values, so inspected code does not directly send the real host environment.
- No inspected file showed filesystem writes, persistence, destructive behavior, or AI-agent control-surface mutation.
Behavioral surface
ChildProcessEnvironmentVarsEvalNetwork
HighEntropyStrings
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
3Cross-file remote execution chain: index.js spawns lib/initializeCaller.js; helper contains network access plus dynamic code execution.
L3: const path = require('path');
L4: const { spawn } = require('child_process');
L5: const { DEFAULT_LEVELS, SORTING_ORDER } = require('./lib/constants');
...
L37: function runBackgroundTask(args) {
L38: const scriptPath = path.resolve(__dirname, './lib/initializeCaller.js');
L39:
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
index.jsView on unpkg · L3•matchType = malicious_source_fingerprint_signature
signature = 3522c2fe164c56ca
signatureType = suspicious_hashes
sourceLabel = Datadog
matchedPackage = dotenv-pack@2.3.10
matchedPath = index.js
matchedIdentity = npm:ZG90ZW52LXBhY2s:2.3.10
similarity = 1.000
shingleOverlap = 12
summary = Datadog malicious npm corpus sample: samples/npm/malicious_intent/dotenv-pack/2.3.10/2026-06-01-dotenv-pack-v2.3.10.zip
High
Findings
6 High3 Medium3 Low
HighChild Processindex.js
HighEvallib/initializeCaller.js
HighSame File Env Network Executionlib/initializeCaller.js
HighCross File Remote Execution Contextindex.js
HighBase64 Obscured Urllib/initializeCaller.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumEnvironment Vars
MediumSecret Patterndocs/transports.md
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to chai-as-smart@2.3.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-as-smart@2.3.5. 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.