Malicious code in @wbnr/design (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1dcfb8ede925ca9e0cf7574c2ba3f81ced56682ef6c54439cc00ad5fc5b960fd) The package's preinstall lifecycle script runs automatically on `npm install`. It reads the installer's username (from USER/USERNAME environment variables) and the machine hostname (via os.hostname()), then embeds those identifiers along with the package name and a timestamp into both a DNS lookup and an HTTPS GET request directed at a hardcoded Burp Collaborator subdomain, 4otph6fase1x2won0hrfzul2wt2qqge5.oastify.com. The package name and scope (@wbnr) and its self-description indicate a dependency-confusion payload targeting an internal organization scope; any environment that resolves @wbnr/design from public npm will leak installer host identifiers to the attacker-controlled out-of-band endpoint. The 'harmless bug bounty PoC' framing in the package description does not change the observable behavior: installer-owned identifiers leave the machine to a third-party OOB collector on install. ## Source: ossf-package-analysis (dbd908eecacbb587e9534c244be33296e6fa11092200cba8428351bb66afe844) The OpenSSF Package Analysis project identified '@wbnr/design' @ 99.3.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
AI Analysis
Technical Summary
The '@wbnr/design' package at version 99.3.0 on npm is flagged as malicious due to its communication with a domain linked to malicious activity. This classification is based on analysis by the OpenSSF Package Analysis project. No additional vulnerability details, exploitation methods, or impact specifics are provided in the source data.
Potential Impact
Use of the '@wbnr/design' package version 99.3.0 may expose users to malicious network communications, potentially leading to compromise or data exfiltration. However, no known exploits in the wild have been reported, and the exact impact is not detailed in the available information.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid using '@wbnr/design' version 99.3.0 and remove it from their projects if present. Monitor the package repository or vendor advisories for updates or official fixes.
Malicious code in @wbnr/design (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1dcfb8ede925ca9e0cf7574c2ba3f81ced56682ef6c54439cc00ad5fc5b960fd) The package's preinstall lifecycle script runs automatically on `npm install`. It reads the installer's username (from USER/USERNAME environment variables) and the machine hostname (via os.hostname()), then embeds those identifiers along with the package name and a timestamp into both a DNS lookup and an HTTPS GET request directed at a hardcoded Burp Collaborator subdomain, 4otph6fase1x2won0hrfzul2wt2qqge5.oastify.com. The package name and scope (@wbnr) and its self-description indicate a dependency-confusion payload targeting an internal organization scope; any environment that resolves @wbnr/design from public npm will leak installer host identifiers to the attacker-controlled out-of-band endpoint. The 'harmless bug bounty PoC' framing in the package description does not change the observable behavior: installer-owned identifiers leave the machine to a third-party OOB collector on install. ## Source: ossf-package-analysis (dbd908eecacbb587e9534c244be33296e6fa11092200cba8428351bb66afe844) The OpenSSF Package Analysis project identified '@wbnr/design' @ 99.3.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
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 '@wbnr/design' package at version 99.3.0 on npm is flagged as malicious due to its communication with a domain linked to malicious activity. This classification is based on analysis by the OpenSSF Package Analysis project. No additional vulnerability details, exploitation methods, or impact specifics are provided in the source data.
Potential Impact
Use of the '@wbnr/design' package version 99.3.0 may expose users to malicious network communications, potentially leading to compromise or data exfiltration. However, no known exploits in the wild have been reported, and the exact impact is not detailed in the available information.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid using '@wbnr/design' version 99.3.0 and remove it from their projects if present. Monitor the package repository or vendor advisories for updates or official fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-11196
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a6b72b09c2644c7f8472235
Added to database: 07/30/2026, 15:50:08 UTC
Last enriched: 07/30/2026, 20:28:33 UTC
Last updated: 09/07/2026, 17:46:32 UTC
Views: 33
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.