# GHSA-4hfc-fv33-ph9p: Malicious Package in sj-tw-abc

> Malicious npm package executes reverse shell code, granting attackers full system control upon installation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-4hfc-fv33-ph9p?

GHSA-4hfc-fv33-ph9p is a vulnerability in sj-tw-abc, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

All versions of `sj-tw-abc` contain malicious code. The package downloads and runs a script that opens a reverse shell in the system.

## Recommendation

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.

## Which versions are affected by GHSA-4hfc-fv33-ph9p?

2 open source packages ship an affected version, including sj-tw-abc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sj-tw-abc` | npm | From 0.0.0 | None |
| `sj-tw-abc` | npm | From 0.0.0 | None |

## How do I fix GHSA-4hfc-fv33-ph9p?

No fix has been published for GHSA-4hfc-fv33-ph9p yet. Limit exposure of the affected software until one is available.

## Is GHSA-4hfc-fv33-ph9p being exploited?

There is no known exploitation of GHSA-4hfc-fv33-ph9p in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4hfc-fv33-ph9p and fix it if it is affected.

What it is: GHSA-4hfc-fv33-ph9p is a vulnerability in sj-tw-abc, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-4hfc-fv33-ph9p in the wild and no public exploit code.

Affected packages and fixed versions:
- sj-tw-abc (npm): affected from 0.0.0; no fix listed
- sj-tw-abc (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4hfc-fv33-ph9p/ (Markdown: https://insights.sbomify.com/GHSA-4hfc-fv33-ph9p/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4hfc-fv33-ph9p

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4hfc-fv33-ph9p/
Summaries are generated and may contain mistakes; the official description above is the record.