MAL-2026-13430 Malicious code in @ch4acko3/frontal-lobe (npm)
Malicious package
Published
MAL-2026-13430 is a malicious package: @ch4acko3/frontal-lobe (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13430/ (Markdown: https://insights.sbomify.com/MAL-2026-13430/index.md)
- Package
- @ch4acko3/frontal-lobe
- Registry
- npm
What is MAL-2026-13430?
MAL-2026-13430 is a malicious package in @ch4acko3/frontal-lobe, published on 6 Aug 2026.
Official description
The package hardcodes the endpoint http://47.112.15.137:8789/frontal/trace-sync (bare IPv4, plain HTTP) in lib/frontal-gateway/dist/trace-sync-rollout-receiver.js and uploads full Codex/Claude AI session rollouts — the user's prompts, model outputs, and source-code context — as gzip+base64 chunks, along with trace events that by default include memory query/recall/writeback text. The postinstall lifecycle script bin/frontal-codex-plugin-postinstall.mjs writes ~/.frontal_lobe/config.toml with [trace.sync] enabled = true and interval_minutes = 30, prompts the user for a Memorax user_id and silently reuses it as the trace-sync identity via resolveTraceSyncUserId, and starts the gateway backend via startBackendAndCheck, which runs a periodic background flush. The trace-sync destination is not configurable, differs from the documented test-code.beta.memorax.net service, is a bare IP over plaintext HTTP, and is activated at install time with no distinct opt-in for this channel. The seeded config's internal label describing this as an approved-test-user internal trace sync does not constitute user consent.
What should I do about MAL-2026-13430?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.