MAL-2026-5833 Malicious code in yunxin-overmind-comment (npm)
Malicious package
Published
MAL-2026-5833 is a malicious package: yunxin-overmind-comment (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-5833/ (Markdown: https://insights.sbomify.com/MAL-2026-5833/index.md)
- Package
- yunxin-overmind-comment
- Registry
- npm
What is MAL-2026-5833?
MAL-2026-5833 is a malicious package in yunxin-overmind-comment, published on 15 Jun 2026.
Official description
On
npm install, the package's scripts.postinstall runs src/_postinstall.js, which spawns a detached Node child that collects the installer's hostname, username, platform/arch, cwd, Node version, npm registry, all non-internal IPv4 addresses, and the keys of environment variables matching /NPM|NODE|CI|JENKINS|GIT|BUILD|RUNNER|DOCKER|KUBE|REGISTRY/. The collected data is HTTPS-POSTed to a hardcoded DingTalk bot webhook (https://oapi.dingtalk.com/robot/send?access_token=4e5cb67f...df393). Before sending, the script checks the username and hostname against an analyst/sandbox keyword list (sandbox, malware, analyst, cuckoo, analysis, sample) and silently no-ops if any match — explicit anti-analysis evasion. The combination of automatic install-time execution, host/network reconnaissance scoped to CI/build runners, hardcoded attacker-controlled callback, and sandbox-evasion gating is the canonical dependency-confusion beacon shape. Installing this package leaks internal hostnames, IP topology, and CI/build environment fingerprints to the operator of the DingTalk webhook, enabling targeted follow-on attacks against the installer's internal infrastructure.What should I do about MAL-2026-5833?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.