Malicious code in @cecm-web-sdk/core (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-18213
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ea27147731ca2c42e40154d06c455a4750a91588b2f8be16e1b237452e20df22) The package ships a postinstall hook (scripts.postinstall: "node beacon.cjs") and a main entry (index.js: require('./beacon.cjs').fire()) that both invoke beacon.cjs. beacon.cjs POSTs a payload containing the package name, os.hostname(), __dirname (install path), process.cwd(), and process.version to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The main module is otherwise a Proxy-based no-op stub with no library functionality; the package's only observable effect is the beacon callback. The destination is a bare IPv4 address over plain HTTP, with no TLS, no pinning, and no caller-configurable override. The behavior fires automatically on `npm install` via the lifecycle hook and again on every `require()` of the package, delivering installer-side host identifiers to a non-first-party endpoint without consent. The package name uses a scope resembling a vendor SDK while shipping no SDK code. ## Source: ghsa-malware (95975e46912705ce591acef6b00c3b11b9dcf9f6ea8f1f89840a77a3ec6134d4) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 23 Oct 2026 02:05:18 UTC
- Source modified
- 25 Oct 2026 15:30:06 UTC
- Observed here
- 25 Oct 2026 16:17:16 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.