Malicious code in nativescript-swisspost-pcc-creative-editor (npm)
The npm package 'nativescript-swisspost-pcc-creative-editor' masquerades as an internal Swiss Post NativeScript package but contains malicious code. During installation, it executes arbitrary Node.js code that leaks the installer's project directory name to a third-party server. This package is a dependency-confusion attack that results in code execution and information disclosure on the installer's system. The package author labels it as a bug bounty proof of concept, but the impact is critical. Any system with this package installed should be considered fully compromised.
AI Analysis
Technical Summary
The 'nativescript-swisspost-pcc-creative-editor' npm package contains malicious code executed during the 'preinstall' lifecycle event. The package reads the installer's project directory name from the environment variable 'INIT_CWD' and sends this information with a timestamp to a hardcoded external callback URL. This behavior constitutes a dependency-confusion attack, allowing arbitrary code execution at install time and leaking sensitive project information. The package pretends to be an internal Swiss Post package but is malicious. The package version explicitly affected is 54.16.3.
Potential Impact
Installation of this package results in arbitrary Node.js code execution on the installer's machine and disclosure of the installer's project directory name to an external attacker-controlled server. This compromises the confidentiality and integrity of the affected system. The vendor advisory states that any computer with this package installed should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different machine. Removal of the package alone does not guarantee full remediation due to potential persistent compromise.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from all affected systems. All secrets and keys stored on compromised machines must be rotated from a separate, trusted device. Due to the severity of the compromise, affected systems should be treated as fully compromised and undergo thorough investigation and remediation beyond package removal.
Malicious code in nativescript-swisspost-pcc-creative-editor (npm)
Description
The npm package 'nativescript-swisspost-pcc-creative-editor' masquerades as an internal Swiss Post NativeScript package but contains malicious code. During installation, it executes arbitrary Node.js code that leaks the installer's project directory name to a third-party server. This package is a dependency-confusion attack that results in code execution and information disclosure on the installer's system. The package author labels it as a bug bounty proof of concept, but the impact is critical. Any system with this package installed should be considered fully compromised.
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 'nativescript-swisspost-pcc-creative-editor' npm package contains malicious code executed during the 'preinstall' lifecycle event. The package reads the installer's project directory name from the environment variable 'INIT_CWD' and sends this information with a timestamp to a hardcoded external callback URL. This behavior constitutes a dependency-confusion attack, allowing arbitrary code execution at install time and leaking sensitive project information. The package pretends to be an internal Swiss Post package but is malicious. The package version explicitly affected is 54.16.3.
Potential Impact
Installation of this package results in arbitrary Node.js code execution on the installer's machine and disclosure of the installer's project directory name to an external attacker-controlled server. This compromises the confidentiality and integrity of the affected system. The vendor advisory states that any computer with this package installed should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different machine. Removal of the package alone does not guarantee full remediation due to potential persistent compromise.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from all affected systems. All secrets and keys stored on compromised machines must be rotated from a separate, trusted device. Due to the severity of the compromise, affected systems should be treated as fully compromised and undergo thorough investigation and remediation beyond package removal.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5793
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-h5g9-q449-jr2c"]
- Ecosystems
- ["npm"]
Threat ID: 6a577eea68715ace43b41295
Added to database: 07/15/2026, 12:36:58 UTC
Last enriched: 09/12/2026, 15:02:32 UTC
Last updated: 09/14/2026, 01:53:32 UTC
Views: 30
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.