# MAL-2026-6335: Malicious code in server-parket (npm)


- **Type:** Malicious package
- **Package:** `server-parket` (npm)
- **Published:** 23 Jun 2026
- **Also known as:** GHSA-mvmx-6c22-q3fm

## What is MAL-2026-6335?

MAL-2026-6335 is a malicious package in server-parket, published on 23 Jun 2026. 

### Official description

package.json declares `postinstall: node test.js`, but test.js is not present in the tarball — installation fails with MODULE_NOT_FOUND and no code executes against the installer. The shipped index.js is a one-line stub containing a broken `console(...)` call (no real functionality). Despite the placeholder content, the package declares axios, form-data, child_process, and os as dependencies — building blocks commonly used for exfiltration scripts — and ships with empty author/description metadata and a 'trial version' message. The current published version causes no installer harm because the referenced payload script is missing, but the shape (stub package + suspicious dep set + lifecycle hook pointing at an unshipped script) is consistent with a placeholder release that could be weaponized in a follow-up version. Routing for human review of maintainer identity and registry context.

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-6335?

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-6335 is a malicious package: server-parket (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-6335/ (Markdown: https://insights.sbomify.com/MAL-2026-6335/index.md)
```

## Sources

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

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