Which versions of copytrade-core are malicious?

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

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

copytrade-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 copytrade-core — how do I know if it already compromised me?

If copytrade-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 copytrade-core part of a known attack campaign?

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

Malicious package

copytrade-corenpm

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

Malicious code in copytrade-core (npm)

MAL-2026-13944

Immediate action

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

npm uninstall copytrade-core

What this malware does

index.js exports a getPlugin function that issues an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/108, takes the response's credits field, passes it to new Function('require','module',...,data.credits), and invokes it with require, module, process, and Buffer injected. This yields arbitrary remote code execution on the consumer's machine, with the fetched payload chosen by whoever controls 31.97.137.157. A separate setDefaultModule function assembles a plausible cdnjs/font-awesome URL from a lookup of legitimate CDN domains (cloudflare.com, fastly.net, etc.) but is never invoked; the exported path uses the bare-IP host instead. Declared dependencies include @primno/dpapi (Windows DPAPI decryption), node-machine-id, and better-sqlite3, matching the toolchain of a browser/wallet credential stealer delivered through this loader.

Malicious versions

1 flagged

2.3.0

Indicators of compromise (SHA-256)

00c8773c5727069f87e54d58cd3679252a90ec0fe3de3a1b4adcb9a3bbff68bd

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 copytrade-core (version 2.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging copytrade-core across your stack and pipelines.
If you installed it — respond
copytrade-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 copytrade-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 copytrade-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. copytrade-core on npm has been identified as a malicious package (version 2.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017651

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks copytrade-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