# GHSA-qv78-398w-cxp7: Malicious Package in shrugging-logging

> Malicious postinstall script in shrugging-logging hijacks npm packages by adding unauthorized maintainers, requiring immediate removal and security review.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2020

## What is GHSA-qv78-398w-cxp7?

GHSA-qv78-398w-cxp7 is a vulnerability in shrugging-logging, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `shrugging-logging` contain malicious code as a postinstall script. The package fetches all names of npm packages owned by the user and attempts to add another maintainer to every package as a means of package hijacking,

## Recommendation

Remove the package from your system. If you own any packages that were compromised please contact npm security immediately at security@npmjs.com. Also enable 2FA for publishing to further secure packages you maintain.

## Which versions are affected by GHSA-qv78-398w-cxp7?

2 open source packages ship an affected version, including shrugging-logging.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shrugging-logging` | npm | All versions | None |
| `shrugging-logging` | npm | All versions | None |

## How do I fix GHSA-qv78-398w-cxp7?

No fix has been published for GHSA-qv78-398w-cxp7 yet. Limit exposure of the affected software until one is available.

## Is GHSA-qv78-398w-cxp7 being exploited?

There is no known exploitation of GHSA-qv78-398w-cxp7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qv78-398w-cxp7 and fix it if it is affected.

What it is: GHSA-qv78-398w-cxp7 is a vulnerability in shrugging-logging, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-qv78-398w-cxp7 in the wild and no public exploit code.

Affected packages and fixed versions:
- shrugging-logging (npm): affected all versions; no fix listed
- shrugging-logging (npm): affected all versions; 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-qv78-398w-cxp7/ (Markdown: https://insights.sbomify.com/GHSA-qv78-398w-cxp7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qv78-398w-cxp7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qv78-398w-cxp7/
Summaries are generated and may contain mistakes; the official description above is the record.