Known malicious package
CertainOur research lists this exact package as malicious.
Listed as malicious in the OSV database.
Malicious
Malicious behaviour found: Our research lists this exact package as malicious. This package does something harmful on purpose. Severity: critical.
Each score comes from what the published files do, not from the README. Rules set every number; the review cannot raise or lower one.
Only behaviour that points to intent is listed here. Ordinary capabilities are in the next section.
Certain · 1Strong · 0Weak · 0
Step-by-step trace: This package loads cleanly without install-time exfiltration or hidden command decoding (on-demand import only, no credential reads, offline / no fixed hosts).
Nothing executes during install; code runs only when imported or called as a tool.
Does not read SSH keys, cloud credential stores, or sensitive environment variables.
All code is plain readable text; no runtime eval, Base64 decoding, or shell spawning.
No fixed external network endpoints or data-collection hosts detected.
Our research lists this exact package as malicious.
In short. Our research reports harmful behaviour here, even though our code analysis found no strong sign on its own. Treat this as malicious.
Many good packages do these things. They are listed so you know what you are installing, and red ones tie into a finding.
| Surface area | Observed behaviour | Status |
|---|---|---|
| Directive & instruction surface | No hidden directives, prompt poisoning, or cross-tool overrides detected in package text. | Clean |
| Context & token footprint | No always-on MCP tool definitions or agent prompt files measured in this package. | Clean |
| Credential & environment reach | No direct credential store or bulk environment reads flagged. | Clean |
| Process & install execution | No install hooks or shell execution traces found. | Clean |
| External network surface | No fixed external network hosts found in static analysis. | Clean |
Nothing notable found.
Nothing runs.
No fixed network destinations found in the code.
No install commands, encoded blobs, or shell execution traces were found in the published files.
0 direct dependencies. None are flagged.
| Check | Result | Outcome |
|---|---|---|
| Lookalike names (a fake copy of a popular package) | 0 of 0 | Pass |
| Installed from a URL instead of the registry | 0 | Pass |
| Known malware advisories (dependencies) | 1 | Flagged |
| Declared but never imported, or brand new | 0 | Pass |
| Published files match the source repository | No mismatch found | Pass |
| Maintainer changed since the last version | Not flagged | Pass |
This package is flagged. Follow the removal and credential-rotation steps below immediately.
Immediate removal command
# DO NOT INSTALL gate-main@0.0.1-security — remove immediately if present:
npm uninstall gate-mainTwo separate reviewers read the evidence on their own. They can confirm intent, but they cannot clear a certain finding or set a grade.
No review was needed for this result.
We read the published files as text and never run, install or import them. Rules turn what the code does into findings, and every grade comes only from those findings. Letter grades: A is 90 and up, B 75, C 60, D 40, F below 40. The overall grade is a weighted average with harmful intent counting most, and it follows the intent score when that falls below 50. Engine version 2.5.3.
Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee. It can miss things, so use it as one input to your own decision.