Malicious code in npm-rce-safe-proof-yourname (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f9fdedc15d959d978bd3563d29d16c5ab226d3c4fa4ab8b6fecf8bdf130e29ab) On `npm install`, postinstall.js runs `whoami`, reads `os.hostname()`, `process.platform`, and `process.version`, and transmits them via HTTPS GET to a hardcoded remote endpoint at https://testnpm.byte.eyes.sh/npm-proof. This fires automatically as a lifecycle hook with no user consent. The package's declared purpose (`npm script for showing date strings`) and its self-labeling as a 'safe proof' do not match the observed behavior — the code is a functional install-time identity beacon transmitting the installer's username and hostname to an author-controlled destination. Beaconing installer identity to a hardcoded third-party host on install is credential/identity leakage regardless of the 'proof' framing.
AI Analysis
Technical Summary
The npm package 'npm-rce-safe-proof-yourname' version 1.0.0 includes a postinstall.js script that runs automatically on installation. This script executes the 'whoami' command, reads system information such as hostname, platform, and Node.js version, and transmits these details to a hardcoded external endpoint (https://testnpm.byte.eyes.sh/npm-proof). This unauthorized data transmission acts as an install-time beacon leaking the installer's identity and system details, representing a privacy and credential leakage vulnerability. The package's stated function as a script for showing date strings is inconsistent with this behavior.
Potential Impact
This vulnerability leads to unauthorized disclosure of the installer's username, hostname, operating system platform, and Node.js version to a remote attacker-controlled server. Such leakage can compromise user privacy and potentially aid attackers in profiling or targeting affected systems. There is no indication of further exploitation beyond this data exfiltration.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid installing 'npm-rce-safe-proof-yourname' version 1.0.0. Review and audit npm packages before installation, especially those with unexpected lifecycle scripts. Monitor for updates or advisories from the package maintainer or npm registry regarding this issue.
Malicious code in npm-rce-safe-proof-yourname (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f9fdedc15d959d978bd3563d29d16c5ab226d3c4fa4ab8b6fecf8bdf130e29ab) On `npm install`, postinstall.js runs `whoami`, reads `os.hostname()`, `process.platform`, and `process.version`, and transmits them via HTTPS GET to a hardcoded remote endpoint at https://testnpm.byte.eyes.sh/npm-proof. This fires automatically as a lifecycle hook with no user consent. The package's declared purpose (`npm script for showing date strings`) and its self-labeling as a 'safe proof' do not match the observed behavior — the code is a functional install-time identity beacon transmitting the installer's username and hostname to an author-controlled destination. Beaconing installer identity to a hardcoded third-party host on install is credential/identity leakage regardless of the 'proof' framing.
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 npm package 'npm-rce-safe-proof-yourname' version 1.0.0 includes a postinstall.js script that runs automatically on installation. This script executes the 'whoami' command, reads system information such as hostname, platform, and Node.js version, and transmits these details to a hardcoded external endpoint (https://testnpm.byte.eyes.sh/npm-proof). This unauthorized data transmission acts as an install-time beacon leaking the installer's identity and system details, representing a privacy and credential leakage vulnerability. The package's stated function as a script for showing date strings is inconsistent with this behavior.
Potential Impact
This vulnerability leads to unauthorized disclosure of the installer's username, hostname, operating system platform, and Node.js version to a remote attacker-controlled server. Such leakage can compromise user privacy and potentially aid attackers in profiling or targeting affected systems. There is no indication of further exploitation beyond this data exfiltration.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid installing 'npm-rce-safe-proof-yourname' version 1.0.0. Review and audit npm packages before installation, especially those with unexpected lifecycle scripts. Monitor for updates or advisories from the package maintainer or npm registry regarding this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10159
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520edb68715ace4391599c
Added to database: 07/11/2026, 09:37:31 UTC
Last enriched: 07/11/2026, 10:04:34 UTC
Last updated: 07/31/2026, 02:22:35 UTC
Views: 32
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.