NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@lizhao1/memorax-code-internalnpm

Advisory published Updated

@lizhao1/memorax-code-internal is a confirmed malicious npm package (MAL-2026-12320) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lizhao1/memorax-code-internal (npm)

MAL-2026-12320
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @lizhao1/memorax-code-internal

What this malware does

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.

Malicious versions

4 flagged
0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

b983c7d55b41a0eb0cd384b7efbdf186926e3e6ce1f88c62c8cf59a96e648285
f4ae94e1d2cc2af7b2aa649bf10616ede12b1f25fef43a5afbc2eeb1675b1675
05e39356232421d8cc201ffbe09dad80142de0a1966d278e5be5895ec492304f
20a03f25c81165c853122032814ee9d7425900686323d31ccea6279c51fe2633

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @lizhao1/memorax-code-internal (4 malicious versions).

  2. If you installed it — respond

    @lizhao1/memorax-code-internal is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @lizhao1/memorax-code-internal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @lizhao1/memorax-code-internal on npm has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014653IN-MAL-2026-014850IN-MAL-2026-015840IN-MAL-2026-016368

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @lizhao1/memorax-code-internal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@lizhao1/memorax-code-internal (npm) malicious package — MAL-2026-12320 | O3 Security