Which versions of coin-fees are malicious?

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

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

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

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

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

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

Malicious package

coin-feesnpm

Advisory published Aug 21, 2026Updated Aug 21, 2026

coin-fees is a confirmed malicious npm package (MAL-2026-14342) 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 coin-fees (npm)

MAL-2026-14342

Immediate action

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

npm uninstall coin-fees

What this malware does

package.json declares a postinstall hook that runs index.js on every install. The script hex-decodes and concatenates a hardcoded destination hostname resolving to gwfqp5cm9r2jfs3d6mjpzt8y5pbkzanz.oastify.com (a Burp Collaborator subdomain), then sleeps a randomized 30-120 seconds and issues HTTP POSTs on port 80 carrying: os.hostname, platform, arch, cwd, whoami/id/uname output, the contents of package.json, the full process.env, the contents of ~/.npmrc (which normally holds npm _authToken values), npm root -g, local port scan results, and Windows recon (ver, tasklist, USERPROFILE). The payload exits silently when CI, GITHUB_ACTIONS, GITLAB_CI, JENKINS_HOME, npm audit/pack/publish flags, /.dockerenv, or docker/kubepods cgroups are detected, and exports a benign-looking function as a facade. The exfiltrated ~/.npmrc auth tokens and environment variables give the operator credentials to publish malicious versions of the installer's other packages and to access CI cloud secrets.

Malicious versions

1 flagged

20.1.1

Indicators of compromise (SHA-256)

f47c61fd59fb65dc8c8932e3e913dd83f18fc8af1d5f06b03cae327228821703

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for coin-fees (version 20.1.1).
If you installed it — respond
coin-fees 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 coin-fees 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. coin-fees 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-018490

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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