yunxin-overmind-comment
This report shows the evidence for yunxin-overmind-comment@1.2.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5833 confirms this npm version as malicious.
Advisory
MAL-2026-5833
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in yunxin-overmind-comment (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to yunxin-overmind-comment@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing yunxin-overmind-comment@1.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.