Which versions of mcp-server-fixthis are malicious?

The following npm versions of mcp-server-fixthis are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.3.0, 0.3.1. Treat any of these as compromised.

How do I remediate mcp-server-fixthis if I installed it?

Remove mcp-server-fixthis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed mcp-server-fixthis — how do I know if it already compromised me?

If mcp-server-fixthis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mcp-server-fixthis part of a known attack campaign?

Yes — mcp-server-fixthis is associated with the GHSA-p45p-rjrm-xmh3, RLMA-2025-05425, RLUA-2025-05886, RLUA-2025-06400 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mcp-server-fixthis across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-fixthis (13 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-fixthis across your stack and pipelines.

Malicious package

mcp-server-fixthisnpm

mcp-server-fixthis is a confirmed malicious npm package (MAL-2025-47929) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mcp-server-fixthis (npm)

MAL-2025-47929

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall mcp-server-fixthis

What this malware does

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.

Malicious versions

13 flagged

0.1.00.1.10.1.20.2.00.2.10.2.20.2.30.2.40.2.50.2.60.2.70.3.00.3.1

Indicators of compromise (SHA-256)

4109cd9a0c196b277a25ff70ae8b8a81ee61aaac82c1d77bbb4e743496508e03

578f35dd6f84276673899faeb3f644e2fbf30248d5f672561665a082e1b4cf0e

58a1cea106a1452eb69d6675e45c36b44c69f0013cd9d6a594e61c940c4e1e1f

6152c62bfa7e409dd76ca804b9e45c732d5137d01c9ae0a031cca0e37372d21a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-fixthis (13 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-fixthis across your stack and pipelines.
If you installed it — respond
Remove mcp-server-fixthis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If mcp-server-fixthis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mcp-server-fixthis before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. mcp-server-fixthis on npm has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p45p-rjrm-xmh3RLMA-2025-05425RLUA-2025-05886RLUA-2025-06400

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks mcp-server-fixthis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database