Malicious code in checkout-get-installment-client-agreement-am (npm)
The npm package 'checkout-get-installment-client-agreement-am' version 35.1.4 contains malicious code that executes upon module load. It detects the host OS and architecture, constructs obfuscated Cloudflare Workers hostnames, and downloads a platform-specific binary payload. This payload is saved under disguised filenames in temporary directories, given executable permissions, and executed detached without signature or hash verification. The code masquerades as telemetry/analytics but exhibits suspicious behavior inconsistent with such claims.
AI Analysis
Technical Summary
This malicious npm package version 35.1.4 includes an _init.js script that, when required, detects the host operating system and architecture, then assembles obfuscated Cloudflare Workers hostnames from split string fragments. It uses a DNS TXT record fallback to *.dl.wel1.ru to download a platform-specific binary payload. The payload is saved to temporary directories with disguised filenames (e.g., dotnet_diag_<hex>.exe on Windows, .cache_<hex> on Unix), permissions are set to executable (chmod 0755), and the binary is spawned detached via /bin/sh or cmd.exe. No signature or hash verification is performed on the downloaded payload. The unconditional execution on module load and obfuscation techniques indicate malicious intent rather than legitimate telemetry.
Potential Impact
The malicious code executes automatically when the package is loaded, potentially allowing execution of arbitrary code on the host system. The downloaded payload runs detached, which could enable persistence or further malicious activity. Lack of signature verification increases risk of executing untrusted code. This compromises system integrity and could lead to unauthorized control or data compromise.
Mitigation Recommendations
No official patch or remediation is currently available. Users should immediately remove and avoid using version 35.1.4 of the 'checkout-get-installment-client-agreement-am' npm package. Verify the integrity of dependencies before installation and monitor for suspicious network activity related to the described domains. Consider using trusted package sources and scanning tools to detect malicious packages.
Malicious code in checkout-get-installment-client-agreement-am (npm)
Description
The npm package 'checkout-get-installment-client-agreement-am' version 35.1.4 contains malicious code that executes upon module load. It detects the host OS and architecture, constructs obfuscated Cloudflare Workers hostnames, and downloads a platform-specific binary payload. This payload is saved under disguised filenames in temporary directories, given executable permissions, and executed detached without signature or hash verification. The code masquerades as telemetry/analytics but exhibits suspicious behavior inconsistent with such claims.
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
This malicious npm package version 35.1.4 includes an _init.js script that, when required, detects the host operating system and architecture, then assembles obfuscated Cloudflare Workers hostnames from split string fragments. It uses a DNS TXT record fallback to *.dl.wel1.ru to download a platform-specific binary payload. The payload is saved to temporary directories with disguised filenames (e.g., dotnet_diag_<hex>.exe on Windows, .cache_<hex> on Unix), permissions are set to executable (chmod 0755), and the binary is spawned detached via /bin/sh or cmd.exe. No signature or hash verification is performed on the downloaded payload. The unconditional execution on module load and obfuscation techniques indicate malicious intent rather than legitimate telemetry.
Potential Impact
The malicious code executes automatically when the package is loaded, potentially allowing execution of arbitrary code on the host system. The downloaded payload runs detached, which could enable persistence or further malicious activity. Lack of signature verification increases risk of executing untrusted code. This compromises system integrity and could lead to unauthorized control or data compromise.
Defensive Guidance
No official patch or remediation is currently available. Users should immediately remove and avoid using version 35.1.4 of the 'checkout-get-installment-client-agreement-am' npm package. Verify the integrity of dependencies before installation and monitor for suspicious network activity related to the described domains. Consider using trusted package sources and scanning tools to detect malicious packages.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12564
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735732bf8831d53913d017
Added to database: 08/05/2026, 15:30:58 UTC
Last enriched: 08/05/2026, 15:54:19 UTC
Last updated: 09/07/2026, 22:00:09 UTC
Views: 18
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.