yunxin-overmind-commentnpm
Advisory published Updated
yunxin-overmind-comment is a confirmed malicious npm package (MAL-2026-5833) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in yunxin-overmind-comment (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for yunxin-overmind-comment (version 1.2.0).
If you installed it — respond
yunxin-overmind-comment 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.
Did it already run?
If yunxin-overmind-comment 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks yunxin-overmind-comment-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.