Which versions of yunxin-overmind-comment are malicious?

The following npm versions of yunxin-overmind-comment are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate yunxin-overmind-comment if I installed it?

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.

I already installed yunxin-overmind-comment — how do I know if it already compromised me?

If yunxin-overmind-comment was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is yunxin-overmind-comment part of a known attack campaign?

Yes — yunxin-overmind-comment is associated with the IN-MAL-2026-006704 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find yunxin-overmind-comment across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for yunxin-overmind-comment (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yunxin-overmind-comment across your stack and pipelines.

Malicious package

yunxin-overmind-commentnpm

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)

MAL-2026-5833

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall yunxin-overmind-comment

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

1 flagged

1.2.0

Indicators of compromise (SHA-256)

57551a10d99024d1d12c7f2e349e6557613ed3a5e036bf45d71129d501fbbabc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for yunxin-overmind-comment (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yunxin-overmind-comment across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks yunxin-overmind-comment before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. yunxin-overmind-comment on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006704

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database