app-sca-info-bankingnpm
Advisory published Updated
app-sca-info-banking is a confirmed malicious npm package (MAL-2026-17182) that executes malicious code on install (malicious version 0.0.24). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in app-sca-info-banking (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for app-sca-info-banking (version 0.0.24).
If you installed it — respond
Remove app-sca-info-banking from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If app-sca-info-banking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks app-sca-info-banking-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.