Which versions of claims-jira-service are malicious?

The following npm versions of claims-jira-service are flagged malicious: 35.8.3. Treat any of these as compromised.

How do I remediate claims-jira-service if I installed it?

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

If claims-jira-service 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 claims-jira-service part of a known attack campaign?

Yes — claims-jira-service is associated with the IN-MAL-2026-015141 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 claims-jira-service across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for claims-jira-service (version 35.8.3).

Malicious package

claims-jira-servicenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

claims-jira-service is a confirmed malicious npm package (MAL-2026-12627) that executes malicious code on install (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claims-jira-service (npm)

MAL-2026-12627

Immediate action

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

npm uninstall claims-jira-service

What this malware does

On require('claims-jira-service'), index.js loads ext.js which downloads a platform-specific executable from author-controlled hosts assembled at runtime by Array.join string-splitting (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS TXT record fallback under *.dl.wel1.ru. The fetched bytes are written to a temp directory under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd. A stamp file with a benign name (.analytics_state) is used to throttle re-execution. Hostnames and payload paths are split across string arrays to defeat static analysis, and DNS-TXT chunking is used as a covert transport channel.

Malicious versions

1 flagged

35.8.3

Indicators of compromise (SHA-256)

666343795502690c0582b4b73652c215ad8f5025ca586d255e94910e8dd59744

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-015141

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks claims-jira-service-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