Malicious code in claims-jira-service (npm)
The npm package 'claims-jira-service' version 35.8.3 contains malicious code that, when required, downloads and executes a platform-specific executable from attacker-controlled hosts. The payload is fetched using obfuscated hostnames and a DNS TXT record fallback, written to temporary files with disguised names, given execute permissions, and run detached from the main process. Execution is throttled using a benignly named stamp file. The obfuscation techniques include string splitting to evade static analysis and covert data transport via DNS TXT chunking.
AI Analysis
Technical Summary
The 'claims-jira-service' npm package version 35.8.3 includes a malicious module that loads an auxiliary script (_ext.js) which downloads an executable payload from multiple attacker-controlled domains assembled dynamically at runtime. The payload is saved to temporary files with disguised names and executed with elevated permissions. The use of DNS TXT records as a fallback channel and string splitting to obfuscate hostnames and payload paths are designed to evade detection. A stamp file named '.analytics_state' is used to limit repeated execution. This behavior constitutes a supply chain compromise through a malicious npm package.
Potential Impact
This malicious package can execute arbitrary code on the host system by downloading and running attacker-controlled executables. This can lead to unauthorized system access, persistence, data exfiltration, or further compromise depending on the payload. The obfuscation and covert communication channels increase the difficulty of detection and mitigation.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package version. Users should immediately remove the 'claims-jira-service' package version 35.8.3 from their environments. Audit and verify all dependencies for integrity and provenance before installation. Monitor for any signs of compromise related to this package. Patch status is not yet confirmed — check the vendor advisory or trusted sources for current remediation guidance.
Malicious code in claims-jira-service (npm)
Description
The npm package 'claims-jira-service' version 35.8.3 contains malicious code that, when required, downloads and executes a platform-specific executable from attacker-controlled hosts. The payload is fetched using obfuscated hostnames and a DNS TXT record fallback, written to temporary files with disguised names, given execute permissions, and run detached from the main process. Execution is throttled using a benignly named stamp file. The obfuscation techniques include string splitting to evade static analysis and covert data transport via DNS TXT chunking.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'claims-jira-service' npm package version 35.8.3 includes a malicious module that loads an auxiliary script (_ext.js) which downloads an executable payload from multiple attacker-controlled domains assembled dynamically at runtime. The payload is saved to temporary files with disguised names and executed with elevated permissions. The use of DNS TXT records as a fallback channel and string splitting to obfuscate hostnames and payload paths are designed to evade detection. A stamp file named '.analytics_state' is used to limit repeated execution. This behavior constitutes a supply chain compromise through a malicious npm package.
Potential Impact
This malicious package can execute arbitrary code on the host system by downloading and running attacker-controlled executables. This can lead to unauthorized system access, persistence, data exfiltration, or further compromise depending on the payload. The obfuscation and covert communication channels increase the difficulty of detection and mitigation.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package version. Users should immediately remove the 'claims-jira-service' package version 35.8.3 from their environments. Audit and verify all dependencies for integrity and provenance before installation. Monitor for any signs of compromise related to this package. Patch status is not yet confirmed — check the vendor advisory or trusted sources for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12627
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735735bf8831d53913f77e
Added to database: 08/05/2026, 15:31:01 UTC
Last enriched: 08/05/2026, 16:14:45 UTC
Last updated: 08/05/2026, 16:14:45 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.