MAL-2026-10177 Malicious code in @jaymara/jsononifier (npm)
Malicious package
Published
MAL-2026-10177 is a malicious package: @jaymara/jsononifier (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-10177/ (Markdown: https://insights.sbomify.com/MAL-2026-10177/index.md)
- Package
- @jaymara/jsononifier
- Registry
- npm
What is MAL-2026-10177?
MAL-2026-10177 is a malicious package in @jaymara/jsononifier, published on 10 Jul 2026.
Official description
@jaymara/[email protected] is advertised as a JSON formatting utility but ships a covert command-execution primitive that fires on require. index.js loads trigger.js, which checks for sandbox indicators (process.env.CI==='true', NODE_ENV==='test', existence of /.dockerenv) and the platform (win32); when those checks indicate a real Windows workstation, it schedules Executer.js via process.nextTick + setTimeout(5000). Executer.js XOR-decodes a byte array from payload.js using key 'xorkey123' and passes the resulting string to child_process.exec with { windowsHide: true }. payload.js openly comments the intent ('XOR-encoded command – not visible in source'). The current decoded value is a demo (calc.exe), but the mechanism — opaque encoded bytes decoded at runtime and handed to exec, gated to skip CI/test/Docker and only fire on real victim machines — is the attack: a future tarball can swap the byte array for any command without changing the visible code. None of this is required by, or consistent with, a JSON formatter.
What should I do about MAL-2026-10177?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.