Malicious code in npm-show-date-proof-strings (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (884f2797ddf6247c906bb97e72b3c0891551b260980811d50c7211ab2ea0bbcf) The package's postinstall.js runs on every `npm install` and collects the installer's username (via `whoami` and `os.userInfo()`), hostname (`os.hostname()`), platform (`process.platform`), and Node version, then transmits them as query parameters via `https.get()` to a hardcoded endpoint at https://testnpm.byte.eyes.sh/npm-proof. The destination is author-controlled and undocumented; the installer has no opportunity to opt out. The package name ("npm-show-date-proof-strings") and an embedded NONCE string ("proof-2026-change-this-random-string") indicate this is a proof-of-execution beacon, but regardless of framing, it is unconsented host-identifier collection on install with no legitimate installer-facing purpose. ## Source: ossf-package-analysis (a2ca450bd74580e87a2f428fd6fcfe66ac30e7a2a88e214da7d3628915549db6) The OpenSSF Package Analysis project identified 'npm-show-date-proof-strings' @ 1.0.3 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.
AI Analysis
Technical Summary
The 'npm-show-date-proof-strings' package versions 1.0.3 and 1.0.4 include a postinstall.js script that runs on every 'npm install'. This script gathers the installer's username (via 'whoami' and 'os.userInfo()'), hostname ('os.hostname()'), platform ('process.platform'), and Node.js version, then transmits these details as query parameters in an HTTPS GET request to a hardcoded endpoint at https://testnpm.byte.eyes.sh/npm-proof. The endpoint is controlled by the package author and undocumented, providing no opt-out for the user. The package appears to function as a proof-of-execution beacon, but effectively performs unconsented host-identifier data collection, which is considered malicious behavior.
Potential Impact
The impact involves unauthorized collection and transmission of potentially sensitive host environment information during package installation. This compromises user privacy and may facilitate further targeted attacks or profiling by the malicious package author. There is no indication of direct code execution beyond data exfiltration, nor evidence of exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing versions 1.0.3 and 1.0.4 of 'npm-show-date-proof-strings'. If already installed, remove the package and audit systems for any unauthorized data transmissions. Monitor vendor advisories for updates or official fixes. Since this is not a cloud service, remediation depends on user action.
Malicious code in npm-show-date-proof-strings (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (884f2797ddf6247c906bb97e72b3c0891551b260980811d50c7211ab2ea0bbcf) The package's postinstall.js runs on every `npm install` and collects the installer's username (via `whoami` and `os.userInfo()`), hostname (`os.hostname()`), platform (`process.platform`), and Node version, then transmits them as query parameters via `https.get()` to a hardcoded endpoint at https://testnpm.byte.eyes.sh/npm-proof. The destination is author-controlled and undocumented; the installer has no opportunity to opt out. The package name ("npm-show-date-proof-strings") and an embedded NONCE string ("proof-2026-change-this-random-string") indicate this is a proof-of-execution beacon, but regardless of framing, it is unconsented host-identifier collection on install with no legitimate installer-facing purpose. ## Source: ossf-package-analysis (a2ca450bd74580e87a2f428fd6fcfe66ac30e7a2a88e214da7d3628915549db6) The OpenSSF Package Analysis project identified 'npm-show-date-proof-strings' @ 1.0.3 (npm) as malicious. It is considered malicious because: - 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 'npm-show-date-proof-strings' package versions 1.0.3 and 1.0.4 include a postinstall.js script that runs on every 'npm install'. This script gathers the installer's username (via 'whoami' and 'os.userInfo()'), hostname ('os.hostname()'), platform ('process.platform'), and Node.js version, then transmits these details as query parameters in an HTTPS GET request to a hardcoded endpoint at https://testnpm.byte.eyes.sh/npm-proof. The endpoint is controlled by the package author and undocumented, providing no opt-out for the user. The package appears to function as a proof-of-execution beacon, but effectively performs unconsented host-identifier data collection, which is considered malicious behavior.
Potential Impact
The impact involves unauthorized collection and transmission of potentially sensitive host environment information during package installation. This compromises user privacy and may facilitate further targeted attacks or profiling by the malicious package author. There is no indication of direct code execution beyond data exfiltration, nor evidence of exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing versions 1.0.3 and 1.0.4 of 'npm-show-date-proof-strings'. If already installed, remove the package and audit systems for any unauthorized data transmissions. Monitor vendor advisories for updates or official fixes. Since this is not a cloud service, remediation depends on user action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6791
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba4968715ace4357e962
Added to database: 07/10/2026, 09:24:25 UTC
Last enriched: 07/10/2026, 09:38:05 UTC
Last updated: 07/31/2026, 11:09:04 UTC
Views: 52
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.