Which versions of create-coin are malicious?

The following npm versions of create-coin are flagged malicious: 20.1.1. Treat any of these as compromised.

How do I remediate create-coin if I installed it?

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

If create-coin was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is create-coin part of a known attack campaign?

Yes — create-coin is associated with the IN-MAL-2026-018572 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 create-coin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for create-coin (version 20.1.1).

Malicious package

create-coinnpm

Advisory published Aug 23, 2026Updated Aug 23, 2026

create-coin is a confirmed malicious npm package (MAL-2026-14372) that steals credentials and exfiltrates sensitive data (malicious version 20.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in create-coin (npm)

MAL-2026-14372

Immediate action

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

npm uninstall create-coin

What this malware does

Package [email protected] registers a postinstall hook that runs build/payload.node.js during npm install. The script performs anti-analysis guards (bails out on CI/GitHub Actions env vars, /.dockerenv, container cgroups, or fewer than four environment variables), sleeps a randomized 10-30 seconds, then reads the installer's ~/.npmrc (or %USERPROFILE%.npmrc), enumerates every process.env entry, and reads project files including package.json, package-lock.json,.env, and src/config.*. It also collects host reconnaissance via os.hostname(), os.userInfo(), and child_process output of uname/id, plus open localhost port probes. All collected data is POSTed over HTTPS to the hardcoded endpoint https://random-name.trycloudflare.com with rejectUnauthorized:false, and a.ran lock file is written for idempotency. Exceptions are swallowed and exit code is forced to 0 so npm install appears successful. The package.json description claims the package is a "netbsd-x64 build for esbuild" while the shipped code has no relationship to esbuild, indicating typosquat / platform-package impersonation of the esbuild family.

Malicious versions

1 flagged

20.1.1

Indicators of compromise (SHA-256)

d92da1d80f455caae769107e4b3ff99c003a296f1238728cfc5521d5be06c380

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for create-coin (version 20.1.1).
If you installed it — respond
create-coin 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 create-coin was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-018572

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks create-coin-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