Which versions of jira-lint are malicious?

The following npm versions of jira-lint are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate jira-lint if I installed it?

Remove jira-lint 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 jira-lint — how do I know if it already compromised me?

If jira-lint 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.

How do I find jira-lint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jira-lint (2 malicious versions).

Malicious package

jira-lintnpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

jira-lint is a confirmed malicious npm package (MAL-2025-49226) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jira-lint (npm)

MAL-2025-49226

Immediate action

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

npm uninstall jira-lint

What this malware does

The package jira-lint was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

c6b162bfbb866437258b70101e3c788048ca508578aacbbdd1341c7713e2ce08

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jira-lint (2 malicious versions).
If you installed it — respond
Remove jira-lint 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 jira-lint 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. jira-lint on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jira-lint-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