# MAL-2026-18198: Malicious code in @pkgship/frpc-linux-amd64 (npm)


- **Type:** Malicious package
- **Package:** `@pkgship/frpc-linux-amd64` (npm)
- **Published:** 22 Oct 2026
- **Also known as:** GHSA-9pc4-vxvx-5676

## What is MAL-2026-18198?

MAL-2026-18198 is a malicious package in @pkgship/frpc-linux-amd64, published on 22 Oct 2026. 

### Official description

Package @pkgship/frpc-linux-amd64@0.71.1 is a platform-specific npm distribution for an frpc binary targeting linux-amd64. No install, preinstall, postinstall, or prepare lifecycle scripts were observed, and no code paths reading installer secrets, performing network exfiltration, fetching remote content for execution, or establishing persistence were observed. The package appears to ship a prebuilt binary artifact as a platform-scoped sub-package, which is the standard pattern for distributing native binaries alongside a parent JS wrapper. Note that frpc is a reverse-proxy / tunneling tool; its runtime capability is exercised only when a user explicitly invokes the binary with their own configuration, not as a consequence of installing this npm package.

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

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-18198 is a malicious package: @pkgship/frpc-linux-amd64 (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-18198/ (Markdown: https://insights.sbomify.com/MAL-2026-18198/index.md)
```

## Sources

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

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