MAL-2026-5570 Malicious code in nim-submit-for-test (npm)
Malicious package
Published
MAL-2026-5570 is a malicious package: nim-submit-for-test (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-5570/ (Markdown: https://insights.sbomify.com/MAL-2026-5570/index.md)
- Package
- nim-submit-for-test
- Registry
- npm
What is MAL-2026-5570?
MAL-2026-5570 is a malicious package in nim-submit-for-test, published on 11 Jun 2026.
Official description
On npm install, the package's postinstall hook executes lib/_compiler.js, which spawns a detached Node process that collects host identity (hostname, username, cwd, IP addresses, npm registry) and the names of environment variables matching NPM|NODE|CI|JENKINS|GIT|BUILD|RUNNER|DOCKER|KUBE|REGISTRY, then POSTs them via https.request to a hardcoded DingTalk webhook (oapi.dingtalk.com/robot/send) with an embedded access token. Before sending, the script checks the installer's username and hostname against an evasion list ('sandbox','malware','analyst','cuckoo','analysis','sample') and exits silently when matched, to avoid running in security analysis environments. The combination of automatic install-time execution, host/CI metadata collection, hardcoded attacker-controlled webhook, and analyst-environment evasion is a clear supply-chain exfiltration beacon.
What should I do about MAL-2026-5570?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.