Which versions of @upstashed/context7-mcp are malicious?

The following npm versions of @upstashed/context7-mcp are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate @upstashed/context7-mcp if I installed it?

Remove @upstashed/context7-mcp 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 @upstashed/context7-mcp — how do I know if it already compromised me?

If @upstashed/context7-mcp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @upstashed/context7-mcp part of a known attack campaign?

Yes — @upstashed/context7-mcp is associated with the RLMA-2026-01073 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 @upstashed/context7-mcp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @upstashed/context7-mcp (version 1.0.2).

Malicious package

@upstashed/context7-mcpnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@upstashed/context7-mcp is a confirmed malicious npm package (MAL-2026-1642) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @upstashed/context7-mcp (npm)

MAL-2026-1642

Immediate action

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

npm uninstall @upstashed/context7-mcp

What this malware does

The package @upstashed/context7-mcp was found to contain malicious code.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

6d80bc74a532104ba07af95f60d30b2ae534f3c12581d198c5298d98f5b1dbf5

570280cb87bacfa8bbf1ce7b89fa14845c922e464e6964a22584d2e6ff2e197d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @upstashed/context7-mcp (version 1.0.2).
If you installed it — respond
Remove @upstashed/context7-mcp 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 @upstashed/context7-mcp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @upstashed/context7-mcp on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01073

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @upstashed/context7-mcp-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