Is @cecm-web-sdk/core malicious?
Yes. Protet confirmed 4 versions of @cecm-web-sdk/core as malicious
First confirmed on 2026-10-22.
Affected versions
| Version | Confirmed | Protet record |
|---|---|---|
| 99.0.1 | 2026-10-22 | PROTET-NPM-2026-28 |
| 3.0.0 | 2026-10-22 | PROTET-NPM-2026-27 |
| 1.1.0 | 2026-10-22 | PROTET-NPM-2026-26 |
| 1.0.1 | 2026-10-22 | PROTET-NPM-2026-25 |
What it does
The package runs node beacon.cjs from its postinstall script, and its index.js runs the same beacon when the module is loaded. The script sends an HTTP POST to http://185.158.107.175:8787/_ah/dc with the package name, the host name, the installation directory, the current working directory and the Node.js version. It does nothing else. The package has no legitimate function: the name and high version numbers match a dependency-confusion attack that reports where an internal package name gets installed.
Impact: whoever runs the receiving server learns which hosts and build systems install the package, and where.
Remediation: remove the package from all projects and lockfiles, pin internal package names to your private registry scope, and review the hosts that installed it.
Indicators
IP addresses185.158.107.175
URLshttp://185.158.107.175:8787/_ah/dc
Other reports
- Also reported in OSV as MAL-2026-18213
What to do if you installed it
- Remove the package from every project that uses it, directly or through another dependency.
- Pin a clean version if you need the package: one that is not listed above and that you have checked yourself, or replace the package. A version missing from this page is not cleared.
- Check your lockfiles (
package-lock.json,yarn.lock,pnpm-lock.yaml) for the affected versions, including as a transitive dependency, and in CI caches. - Rotate credentials that were reachable from any machine or build that installed it: npm and GitHub tokens, cloud keys, SSH keys, and secrets in environment variables or CI settings.
Status history
- 2026-10-22: 1.0.1, 1.1.0, 3.0.0, 99.0.1 named by Protet Intel