Bawwab: Top 302 scan

@aashari/mcp-server-atlassian-jira

Not malicious, needs a look Reviewed: expected behaviour

Bawwab's static rules found patterns that deserve a human look. This is not a finding that the package is malicious; the review notes below say what each pattern turned out to be.

Why it was flagged

The static rules marked this “Not malicious, needs a look” because of:

Kind
MCP server
Source
npm
Version
3.3.0
Popularity
21,667 npm downloads/week (2026-11-20)
Link
https://www.npmjs.com/package/@aashari/mcp-server-atlassian-jira/v/3.3.0
Scanned
2026-11-20T22:32:46+00:00
Scan time
2.3 s
Review note: A postinstall that only marks the CLI executable, and a standard .env config loader; nothing malicious.

Findings (2)

install-script: Runs code at install time med

package.json:18

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesOWASP Agentic ASI05 Unexpected Code Execution (RCE)MITRE ATLAS AML.T0010.001 Supply Chain Compromise: SoftwareMITRE ATLAS AML.T0011.001 User Execution: Malicious Package

node scripts/ensure-executable.js

What this means: Install hooks run automatically with your privileges before you can review anything.

The rule's general advice: Read the script; prefer packages with no install hooks. (see the review note for this case)

Expected for what this tool does

postinstall runs scripts/ensure-executable.js, which only chmods dist/index.js to 755 when it isn't executable already. No network access, no other files.

Reviewed by Claude (AI-assisted review), 2026-11-21

credential-access: Touches credentials or secrets high

dist/utils/config.util.js:59

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI03 Identity and Privilege AbuseOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0055 Unsecured CredentialsMITRE ATLAS AML.T0083 Credentials from AI Agent Configuration

methodLogger.debug('[src/utils/config.util.ts@loadFromEnvFile] No .env file found or error reading it');

What this means: Reads files or environment holding keys, tokens or sessions.

The rule's general advice: Confirm the tool needs this; otherwise do not install. (see the review note for this case)

Expected for what this tool does

The config loader calls dotenv to read Jira settings from a .env file, alongside a global config file and env vars. This is how the server is documented to be configured.

Reviewed by Claude (AI-assisted review), 2026-11-21

1 low-severity notes (informational, do not affect the result)

install-script: Runs code at install time low

package.json:17

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesOWASP Agentic ASI05 Unexpected Code Execution (RCE)MITRE ATLAS AML.T0010.001 Supply Chain Compromise: SoftwareMITRE ATLAS AML.T0011.001 User Execution: Malicious Package

npm run build && node scripts/ensure-executable.js

What this means: Install hooks run automatically with your privileges before you can review anything.

The rule's general advice: Read the script; prefer packages with no install hooks. (see the review note for this case)

Expected for what this tool does

postinstall runs scripts/ensure-executable.js, which only chmods dist/index.js to 755 when it isn't executable already. No network access, no other files.

Reviewed by Claude (AI-assisted review), 2026-11-21

Dispute this result

Maintainer and think this is wrong? Open a dispute on GitHub with the target id mcp-npm-aashari-mcp-server-atlassian-jira-36ea09.