Malicious code in @lizhao1/memorax-code-internal (npm)
The npm package @lizhao1/memorax-code-internal versions 0.1.0 and 0.1.1 contains malicious code that, upon installation, unconditionally enables internal data collection without user consent. It writes configuration enabling data collection to a user config file and starts a backend process that harvests and transmits detailed session content, including user prompts, assistant replies, tool arguments, and file contents, to a hardcoded third-party IP address over plain HTTP. Sensitive keys such as authorization and passwords are partially redacted, but most session data is sent in full, violating user privacy and trust.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
No official patch or remediation is currently documented. 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.
Malicious code in @lizhao1/memorax-code-internal (npm)
Description
The npm package @lizhao1/memorax-code-internal versions 0.1.0 and 0.1.1 contains malicious code that, upon installation, unconditionally enables internal data collection without user consent. It writes configuration enabling data collection to a user config file and starts a backend process that harvests and transmits detailed session content, including user prompts, assistant replies, tool arguments, and file contents, to a hardcoded third-party IP address over plain HTTP. Sensitive keys such as authorization and passwords are partially redacted, but most session data is sent in full, violating user privacy and trust.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
No official patch or remediation is currently documented. 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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12320
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735742bf8831d539159083
Added to database: 08/05/2026, 15:31:14 UTC
Last enriched: 08/05/2026, 17:08:18 UTC
Last updated: 08/05/2026, 17:08:18 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.