Which versions of docsmate-docsmate-core are malicious?

The following npm versions of docsmate-docsmate-core are flagged malicious: 35.9.3. Treat any of these as compromised.

How do I remediate docsmate-docsmate-core if I installed it?

docsmate-docsmate-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.

I already installed docsmate-docsmate-core — how do I know if it already compromised me?

If docsmate-docsmate-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.

Is docsmate-docsmate-core part of a known attack campaign?

Yes — docsmate-docsmate-core is associated with the IN-MAL-2026-015716 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 docsmate-docsmate-core 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 docsmate-docsmate-core (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging docsmate-docsmate-core across your stack and pipelines.

Malicious package

docsmate-docsmate-corenpm

docsmate-docsmate-core is a confirmed malicious npm package (MAL-2026-13281) that steals credentials and exfiltrates sensitive data (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in docsmate-docsmate-core (npm)

MAL-2026-13281

Immediate action

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

npm uninstall docsmate-docsmate-core

What this malware does

On require(), index.js loads support.js which assembles Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev and siblings cf100-416, cf101-adf, cf102-baf) from split string fragments, with a DNS-TXT fallback resolver chain across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. It downloads an OS/arch-specific binary over HTTPS, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods 0755, and detaches it via spawn('/bin/sh', ['-c', path+' &'], {detached:true}) or spawn('cmd',...). A stamp file suppresses re-runs and environment variables can disable execution. The package presents itself as a platform/core types library and ships no shipped native source that would justify fetching and executing an opaque binary at import time. Destination hosts are string-obfuscated to evade static inspection, and the dropped file is named to impersonate a Microsoft.NET diagnostic tool.

Malicious versions

1 flagged

35.9.3

Indicators of compromise (SHA-256)

9bbdf7679d49cff873276c1d1690dfc93f5ff274d383915a2ce9f115e7403e1e

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 docsmate-docsmate-core (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging docsmate-docsmate-core across your stack and pipelines.
If you installed it — respond
docsmate-docsmate-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 docsmate-docsmate-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 docsmate-docsmate-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

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

Campaign

IN-MAL-2026-015716

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks docsmate-docsmate-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database