Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in @vpms/design-system (npm)

0
Critical
Published: 06/25/2026 (06/25/2026, 17:20:53 UTC)
Source: GCVE Database
Product: @vpms/design-system

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (43ce5813fba2660b094a3e8a5c5a0bf2f1972530c294830c0a2e3d15dcd1b096) package.json declares preinstall="node index.js". On every npm install, index.js iterates process.env and harvests any variable whose name contains SECRET/TOKEN/PASSWORD/KEY/CREDENTIAL, plus an explicit list of high-value secrets (NPM_TOKEN, GITHUB_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AZURE_CLIENT_SECRET, GOOGLE_APPLICATION_CREDENTIALS, etc.). It also collects os.hostname(), os.userInfo().username, process.cwd(), process.platform, process.arch, and the output of execSync('ps -eo pid,pcpu,pmem,user,comm --sort=-pcpu | head -n 8'). The collected JSON is POSTed via https.request to a hardcoded Pipedream endpoint at eov0bmnid410yqf.m.pipedream.net. The package self-labels as a "PenTest design system" / canary but ships no design-system code — the main entry is solely the exfiltration script, and the @vpms scope appears to target an internal organization namespace (dependency-confusion shape). Self-labeling as a "pentest canary" does not excuse unsolicited bulk credential exfiltration from installers who never consented to a pentest scope. ## Source: ghsa-malware (537bc45c39817d78b733d2a67cdfbccfd9f638dfa184f151ed65ec597131c507) 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 (321dc26d64d28a5a4f4d59f0d719944570cccc7e16173b205160b2db4e04720e) The OpenSSF Package Analysis project identified '@vpms/design-system' @ 0.1.3 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Affected software

npmghsa
@vpms/design-system
Affected versions
=0.1.3=1.0.0=1.1.2=1.0.1

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

AILast updated: 06/26/2026, 22:41:52 UTC

Technical Analysis

The '@vpms/design-system' npm package versions 0.1.3, 1.0.0, 1.0.1, and 1.1.2 include a preinstall script that executes 'node index.js' on installation. This script iterates over environment variables to harvest any containing keywords like SECRET, TOKEN, PASSWORD, KEY, or CREDENTIAL, including specific high-value secrets such as NPM_TOKEN, GITHUB_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AZURE_CLIENT_SECRET, and GOOGLE_APPLICATION_CREDENTIALS. It also collects system information such as hostname, username, current working directory, platform, architecture, and top CPU-consuming processes. The collected data is sent via HTTPS POST to a hardcoded Pipedream endpoint associated with malicious activity. The package does not contain legitimate design system code and appears to be a malicious package targeting internal organization namespaces via dependency confusion techniques.

Potential Impact

This malicious package can lead to unauthorized disclosure of sensitive credentials and environment information from any system where it is installed. The exfiltrated data includes high-value secrets that could allow attackers to compromise cloud accounts, source code repositories, and other critical infrastructure. This poses a significant risk of credential theft and subsequent unauthorized access or lateral movement within affected environments.

Mitigation Recommendations

Users should immediately remove the affected versions (=0.1.3, =1.0.0, =1.0.1, =1.1.2) of the '@vpms/design-system' package from their projects. Avoid installing or updating to these versions. Audit systems for any signs of credential compromise if these versions were installed. Since no official patch or fix is available, do not use this package. Consider implementing strict package source verification and dependency auditing to prevent installation of malicious packages. Monitor for any suspicious activity related to exposed credentials.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-6467
Osv Schema Version
1.7.4
Aliases
[]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a3ef7e027e9c7971902c221

Added to database: 06/26/2026, 22:06:24 UTC

Last enriched: 06/26/2026, 22:41:52 UTC

Last updated: 07/28/2026, 20:31:07 UTC

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses