Cyberchef MCP Server

cyberchef npm v11.2.0 Source verified

Published by gchq — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
F
34/100
Last scanned
Trust
F · 34/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
F Why this grade 100 − 66 = 34/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−37.7 Obfuscated / encoded payload in server code ×10 MTC-SRC-004 injection
−22 Hardcoded PEM private key in server code MTC-SRC-008 exfiltration
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 14

high Hardcoded PEM private key in server code (tests/operations/tests/ECDSA.mjs)MTC-SRC-008

A live-looking PEM private key is hardcoded in `tests/operations/tests/ECDSA.mjs:16`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: PEM private key: ----…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server tests/operations/tests/ECDSA.mjs

high Obfuscated / encoded payload in server code (tests/browser/01_io.js)MTC-SRC-004

In the server's implementation (`tests/browser/01_io.js:36`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/browser/01_io.js

high Obfuscated / encoded payload in server code (tests/operations/tests/AvroToJSON.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/AvroToJSON.mjs:36`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x4f\x62\x6a\x01\x04\x16\x61\x76\x72\x6f\x2e\x73\x63\x68\x65\x6d\x61\x96\x01\x7b\x22\x74\x79\x70\x65\x22\x3a\x22\x72\x65

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/AvroToJSON.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/Base32.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/Base32.mjs:21`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/Base32.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/Base64.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/Base64.mjs:12`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/Base64.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/Base85.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/Base85.mjs:19`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/Base85.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/ByteRepr.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/ByteRepr.mjs:11`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/ByteRepr.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/CRCChecksum.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/CRCChecksum.mjs:11`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/CRCChecksum.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/CaretMdecode.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/CaretMdecode.mjs:30`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f\x20\x21\x22\x23\x24\x25\x26\x27

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/CaretMdecode.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/CipherSaber2.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/CipherSaber2.mjs:26`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x6f\x6d\x0b\xab\xf3\xaa\x67\x19\x03\x15\x30\xed\xb6\x77

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/CipherSaber2.mjs

high Obfuscated / encoded payload in server code (tests/operations/tests/Comment.mjs)MTC-SRC-004

In the server's implementation (`tests/operations/tests/Comment.mjs:12`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/Comment.mjs

high Shell/command execution in server code (tests/operations/tests/Code.mjs)MTC-SRC-002

In the server's implementation (`tests/operations/tests/Code.mjs:334`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/operations/tests/Code.mjs

high Shell/command execution in server code (webpack.config.js)MTC-SRC-002

In the server's implementation (`webpack.config.js:125`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server webpack.config.js

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"cyberchef" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package cyberchef

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v11.2.0 latest F 34/100 14 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: F · 34/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cyberchef/badge.svg)](https://mcptrustchecker.com/registry/cyberchef)
HTML
<a href="https://mcptrustchecker.com/registry/cyberchef"><img src="https://mcptrustchecker.com/registry/cyberchef/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cyberchef/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cyberchef --online

Use the free API → How scoring works

More in Security & Testing