sme-crm-services-sme-crm-services-corenpm
sme-crm-services-sme-crm-services-core is a confirmed malicious npm package (MAL-2026-12438) that steals credentials and exfiltrates sensitive data (malicious version 20.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sme-crm-services-sme-crm-services-core (npm)
What this malware does
On require() of the package, index.js loads vendor.js which selects an OS/architecture-specific URL path, downloads an opaque binary over HTTPS from Cloudflare Workers subdomains whose hostnames are assembled by Array.join from small string fragments (oob-worker.cf102-baf.workers.dev, cf103-070.workers.dev, cf100-416.workers.dev), with a DNS TXT fallback under *.dl.well1.site. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names such as dotnet_diag<hex>.exe or.cache_<hex>, chmod'd 0755, and executed detached via spawn('/bin/sh','-c',...) or cmd.exe /c start. Environment variables DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK gate activity and a /tmp/.analytics_state stamp file rate-limits re-execution. A sibling file lib/telemetry.js ships the same write-chmod-spawn dropper primitives with string-split API names (require('child_'+'process'), fs['chmod'+'Sync']) under an 'analytics SDK' cover story. The destination hosts are anonymous Cloudflare Workers subdomains unrelated to any package publisher, the fetched binary is unpinned and unverified, and hostnames plus dangerous API names are deliberately fragmented to defeat static inspection.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sme-crm-services-sme-crm-services-core (version 20.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sme-crm-services-sme-crm-services-core across your stack and pipelines.
If you installed it — respond
sme-crm-services-sme-crm-services-core 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 sme-crm-services-sme-crm-services-core 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 sme-crm-services-sme-crm-services-core 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sme-crm-services-sme-crm-services-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.