Malicious code in swiper_angular (npm)

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (35a523a0f2bb0df423657f50e42be71ae87d3071b859e1f4eb88a90709ba0ca5) Package name typosquats swiper/swiper-angular at implausible version 5.9999.1. The preinstall.js script runs at install time and collects installer host identity and network context — os.hostname(), os.userInfo() username, current working directory, package name, git remote domain, /etc/resolv.conf search domain, /etc/hosts and /etc/hostname content grepped for 'tbi|beez|tbibank', egress IP via `ip route get 1.1.1.1` and `curl -s ifconfig.me`, and environment variable names filtered against the same organization tokens. The collected fields are concatenated into a query string and sent via https.get to the hardcoded Interactsh subdomain rmknhtfmmidejheotogony3qpqrk75wdz.oast.fun/cb2. Behavior fires automatically on npm install with no consent prompt and targets a specific organization (tbibank) regardless of the self-applied 'security research' label. ## Source: ghsa-malware (75ec7c266ed95505d5aefd1c335f36ca6ce46ea4545dd437f2458f793601483e) 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. ## Source: ossf-package-analysis (474db4780bfc49ff2146966bdd508c123baf4d39c636e27aaba1996a0016d8f6) The OpenSSF Package Analysis project identified 'swiper_angular' @ 5.9999.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Source published

25 Jul 2026 16:30:40 UTC

Source modified

28 Sep 2026 07:00:08 UTC

Saved here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.