Which versions of pump-fun-skills are malicious?

The following npm versions of pump-fun-skills are flagged malicious: 20.1.1. Treat any of these as compromised.

How do I remediate pump-fun-skills if I installed it?

pump-fun-skills 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 pump-fun-skills — how do I know if it already compromised me?

If pump-fun-skills 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 pump-fun-skills part of a known attack campaign?

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

Malicious package

pump-fun-skillsnpm

pump-fun-skills is a confirmed malicious npm package (MAL-2026-14262) 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 pump-fun-skills (npm)

MAL-2026-14262

Immediate action

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

npm uninstall pump-fun-skills

What this malware does

The package's postinstall script (index.js) auto-runs on npm install and collects a broad set of installer-side data — hostname, full process.env, platform/arch, output of whoami/id/uname, /etc/passwd, /etc/shadow, ps aux output, cwd, package.json, node_modules listing, ~/.npmrc, and the most recent ~/.npm/_logs files — and POSTs each item over plain HTTP to the hardcoded attacker-controlled host 6lsgfv2czhs95it3wc9fpjyovf19pzdo.oastify.com (a Burp Collaborator subdomain). Reading ~/.npmrc harvests the installer's npm registry auth token, enabling downstream hijack of packages published under the installer's identity. The package name and reconnaissance commands additionally search the filesystem for directories matching pump.fun and padre.gg, and package.json falsely describes the package as an esbuild netbsd-x64 build — a typosquat/impersonation lure targeting developers in those crypto-frontend ecosystems.

Malicious versions

1 flagged

20.1.1

Indicators of compromise (SHA-256)

5818b39f1e4fbd315379ea5b32209ab3a57edb3532a948203910b3fb74bec49e

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pump-fun-skills-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