Malicious code in @leejungkiin/awkit (npm)
The npm package @leejungkiin/awkit contains malicious code that executes during installation. It runs a script that fetches and executes a shell script from a third-party GitHub repository on an unpinned mutable branch, allowing remote code execution with full shell privileges. The malicious script can modify the environment, install additional binaries, or exfiltrate data. Multiple specific versions of the package are affected.
AI Analysis
Technical Summary
The @leejungkiin/awkit npm package includes a lifecycle install script (scripts/dependency-manager.js) that executes a curl command to fetch and run a shell script from the rtk-ai/rtk GitHub repository's master branch, which is not pinned to a specific commit. This introduces a remote code execution vulnerability because the fetched script is controlled by a third party unrelated to the package scope. The script collects platform and home directory information and has full shell privileges, enabling environment modification, further binary installation, or data exfiltration. Additional bundled code uses child_process and hardcoded HTTP endpoints, indicating further potentially malicious behavior. Multiple exact versions of the package are affected.
Potential Impact
This vulnerability allows an attacker controlling the third-party GitHub repository to execute arbitrary code on the machine installing the package with full shell privileges. This can lead to environment compromise, installation of additional malicious binaries, and exfiltration of sensitive host data. Because the malicious script is fetched dynamically from an unpinned branch, the attack surface is persistent and can be updated by the attacker at any time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or updating to the affected versions of @leejungkiin/awkit. Audit and block network access to the malicious third-party domains (raw.githubusercontent.com/rtk-ai/rtk and www.rtk-ai.app) during installation. Consider using package integrity verification or locking dependencies to trusted versions. Monitor for updates from the package maintainer or npm advisories for any official fixes.
Malicious code in @leejungkiin/awkit (npm)
Description
The npm package @leejungkiin/awkit contains malicious code that executes during installation. It runs a script that fetches and executes a shell script from a third-party GitHub repository on an unpinned mutable branch, allowing remote code execution with full shell privileges. The malicious script can modify the environment, install additional binaries, or exfiltrate data. Multiple specific versions of the package are affected.
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 @leejungkiin/awkit npm package includes a lifecycle install script (scripts/dependency-manager.js) that executes a curl command to fetch and run a shell script from the rtk-ai/rtk GitHub repository's master branch, which is not pinned to a specific commit. This introduces a remote code execution vulnerability because the fetched script is controlled by a third party unrelated to the package scope. The script collects platform and home directory information and has full shell privileges, enabling environment modification, further binary installation, or data exfiltration. Additional bundled code uses child_process and hardcoded HTTP endpoints, indicating further potentially malicious behavior. Multiple exact versions of the package are affected.
Potential Impact
This vulnerability allows an attacker controlling the third-party GitHub repository to execute arbitrary code on the machine installing the package with full shell privileges. This can lead to environment compromise, installation of additional malicious binaries, and exfiltration of sensitive host data. Because the malicious script is fetched dynamically from an unpinned branch, the attack surface is persistent and can be updated by the attacker at any time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing or updating to the affected versions of @leejungkiin/awkit. Audit and block network access to the malicious third-party domains (raw.githubusercontent.com/rtk-ai/rtk and www.rtk-ai.app) during installation. Consider using package integrity verification or locking dependencies to trusted versions. Monitor for updates from the package maintainer or npm advisories for any official fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13427
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cf89bf8831d5391ada0f
Added to database: 08/06/2026, 18:16:41 UTC
Last enriched: 08/06/2026, 18:30:17 UTC
Last updated: 08/07/2026, 00:35:40 UTC
Views: 3
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.
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.