Which versions of pump-segments-sdk are malicious?

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

How do I remediate pump-segments-sdk if I installed it?

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

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

Yes — pump-segments-sdk is associated with the IN-MAL-2026-018233 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-segments-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pump-segments-sdk (version 20.1.1).

Malicious package

pump-segments-sdknpm

pump-segments-sdk is a confirmed malicious npm package (MAL-2026-14186) 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-segments-sdk (npm)

MAL-2026-14186

Immediate action

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

npm uninstall pump-segments-sdk

What this malware does

package.json declares a postinstall hook that runs index.js on install. The script collects the installer's hostname, full process.env, platform info, output of whoami/uname/id/ps aux, cwd, package.json, node_modules listing, /etc/passwd, /etc/shadow, ~/.npmrc, and ~/.npm/_logs, and POSTs the collected data over plain HTTP to a hardcoded oastify.com (Burp Collaborator) subdomain. The package presents itself as a netbsd-x64 esbuild build, which does not match the observed behavior. The read of ~/.npmrc exposes any npm auth tokens present on the installer host, and /etc/shadow read attempts to exfiltrate local password hashes.

Malicious versions

1 flagged

20.1.1

Indicators of compromise (SHA-256)

838470d6049e677964786698e4a7a5dca5897ce2623d54a4c3e84510381e74e5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pump-segments-sdk (version 20.1.1).
If you installed it — respond
pump-segments-sdk 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-segments-sdk 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. pump-segments-sdk 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-018233

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pump-segments-sdk-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