Malicious code in @open-banking/cabinet-providers (npm)
Description
The npm package @open-banking/cabinet-providers versions 999.9.2 and 999.9.5 contains malicious code that executes automatically upon installation. It exfiltrates sensitive system information including the contents of /etc/passwd and host identity data by sending them to attacker-controlled endpoints. This behavior occurs without user consent during the npm install process, posing a severe risk to any system where the package is installed.
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 package @open-banking/[email protected] is a dependency-confusion bait package with an anomalously high version number under a generic scope. Its package.json specifies a postinstall script that sends the contents of /etc/passwd to a Burp Collaborator (OAST) endpoint using curl. Additionally, a bundled script hex-encodes the hostname, home directory, and username, splitting the data into chunks sent as DNS-style subdomains to another OAST endpoint. Both data exfiltration actions occur automatically during npm install without user consent. This behavior effectively compromises the host by leaking sensitive system information to an external attacker.
Potential Impact
Any system that installs this package is at high risk of compromise due to automatic exfiltration of sensitive system files and host identity information. The presence of this package indicates a full compromise, and all secrets and keys on the affected system should be considered exposed and rotated immediately. Removing the package alone may not eliminate all malicious artifacts or backdoors introduced during installation.
Defensive Guidance
There is no official patch or fix available for this malicious package. The recommended mitigation is to immediately remove the package from all affected systems. All secrets, credentials, and keys stored on compromised systems should be rotated from a secure, unaffected environment. Due to the severity of the compromise, affected systems should be thoroughly audited and potentially rebuilt to ensure no persistent malicious code remains.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5392
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-423v-5hgq-8rxh","GHSA-r2wq-c8cp-gp8h"]
- Ecosystems
- ["npm"]
Threat ID: 6a96f31bacd9273b49e49993
Added to database: 09/01/2026, 15:45:31 UTC
Last enriched: 09/08/2026, 06:08:25 UTC
Last updated: 10/04/2026, 07:45:53 UTC
Views: 23
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.