# MAL-2026-17182: Malicious code in app-sca-info-banking (npm)


- **Type:** Malicious package
- **Package:** `app-sca-info-banking` (npm)
- **Published:** 25 Sep 2026
- **Also known as:** GHSA-v2r2-pcp9-6mxr

## What is MAL-2026-17182?

MAL-2026-17182 is a malicious package in app-sca-info-banking, published on 25 Sep 2026. 

### Official description

package.json declares scripts.postinstall: `node poc.js`, causing poc.js to execute automatically on npm install. poc.js issues DNS (dns.resolve4) and HTTP (http.get) callbacks to unique subdomains under ki6rmdjnq5q8y7v8soxc080fz65ytohd.oastify.com (a Burp Suite Collaborator / OAST host) and writes a marker file under os.tmpdir(). The package's main entry is an empty stub (module.exports = {}); the postinstall payload is the package's only functionality. The DNS/HTTP callbacks to an attacker-controlled OAST domain confirm arbitrary code execution on the installer's host and leak install-event metadata to a third-party endpoint.

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.

The OpenSSF Package Analysis project identified 'app-sca-info-banking' @ 0.0.24 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-17182?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17182 is a malicious package: app-sca-info-banking (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17182/ (Markdown: https://insights.sbomify.com/MAL-2026-17182/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17182

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17182/
Summaries are generated and may contain mistakes; the official description above is the record.