MalwarePublished 5 Aug 2026Updated 6 Aug 2026

@lizhao1/memorax-code-internal (npm) · Malicious Code

Affects @lizhao1/memorax-code-internalSource GCVE Database

Malicious package : remove @lizhao1/memorax-code-internal and rotate any secrets on hosts that installed it.

Data as of 6 Aug 2026, 18:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-12320

What to do

Remove @lizhao1/memorax-code-internal from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@lizhao1/memorax-code-internal	Affected =0.1.0 =0.1.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b983c7d55b41a0eb0cd384b7efbdf186926e3e6ce1f88c62c8cf59a96e648285) The npm postinstall script (bin/memorax-code-plugin-postinstall.mjs) unconditionally calls enableInternalDataCollectionConfig() with no user prompt, writing internal.data_collection.enabled=true and a self-defined consent string into ~/.memorax-code/config.toml, then starts a backend that harvests and transmits Codex and Claude Code session content. The backend module lib/memorax-code-backend/dist/internal-trace-collection-config.js hardcodes the destination http://47.112.192.211:8789/memorax-code/trace-collection (bare IP, plain HTTP, Alibaba Cloud netblock — not matching the advertised publisher domain code.memorax.net). flushInternalTraceCollection reads per-session events.jsonl and native rollout files for the configured AI clients and POSTs them in batches to that endpoint. Only a narrow allow-list of key names (authorization/api_key/secret/password) is redacted; user prompts, assistant replies, tool arguments, and file contents embedded in session events are transmitted in full. The 'consent' gate is satisfied by the postinstall itself writing the accepted consent-version string, and the pipeline is labeled 'internal data collection' / 'anonymous' despite shipping full session bodies to a hardcoded third-party endpoint.

Impact

This malicious behavior results in unauthorized exfiltration of potentially sensitive user session data, including prompts, replies, tool arguments, and file contents, to an external third-party server without explicit user consent. This compromises user privacy and may expose confidential or proprietary information. The use of plain HTTP and a hardcoded IP address increases the risk of interception and misuse of the data. The package undermines trust in the software supply chain by embedding covert data harvesting functionality.

Defensive guidance

Users should avoid installing or using versions 0.1.0 and 0.1.1 of @lizhao1/memorax-code-internal. Remove these versions if already installed and monitor for updates or advisories from the package maintainers or npm security teams. Since the package is not a cloud service, remediation depends on user action. Check the vendor or npm advisories for any future fixes or removal notices.

Summary

The npm package @lizhao1/memorax-code-internal (versions 0.1.0 and 0.1.1) includes a postinstall script that automatically calls enableInternalDataCollectionConfig(), writing a consent string and enabling data collection in ~/.memorax-code/config.toml without user interaction. It then launches a backend module that collects Codex and Claude Code session data, including user inputs and assistant outputs, and sends this data in batches via HTTP POST to a hardcoded IP address (http://47.112.192.211:8789/memorax-code/trace-collection) hosted on Alibaba Cloud. Only a narrow allow-list of sensitive keys is redacted; the rest of the session content is transmitted in clear text. The consent mechanism is effectively bypassed by the postinstall script itself, and the data collection is misleadingly labeled as 'internal' and 'anonymous' despite sending full session bodies to an external third party.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Aug 2026, 17:08 UTC

Technical details

References

Community reviews