Which versions of swiper_angular are malicious?

The following npm versions of swiper_angular are flagged malicious: 5.9999.0, 5.9999.1. Treat any of these as compromised.

How do I remediate swiper_angular if I installed it?

swiper_angular 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 swiper_angular — how do I know if it already compromised me?

If swiper_angular 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 swiper_angular part of a known attack campaign?

Yes — swiper_angular is associated with the IN-MAL-2026-011243, IN-MAL-2026-014839 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 swiper_angular 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 swiper_angular (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swiper_angular across your stack and pipelines.

Malicious package

swiper_angularnpm

swiper_angular is a confirmed malicious npm package (MAL-2026-11065) that steals credentials and exfiltrates sensitive data (malicious versions 5.9999.0, 5.9999.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in swiper_angular (npm)

MAL-2026-11065

Immediate action

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

npm uninstall swiper_angular

What this malware does

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.

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.

Malicious versions

2 flagged

5.9999.05.9999.1

Indicators of compromise (SHA-256)

474db4780bfc49ff2146966bdd508c123baf4d39c636e27aaba1996a0016d8f6

af00e41bdc43d8aa468c73cbb63251cd85bbf40dd3cd0d57f38abeee77dc2559

35a523a0f2bb0df423657f50e42be71ae87d3071b859e1f4eb88a90709ba0ca5

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 swiper_angular (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swiper_angular across your stack and pipelines.
If you installed it — respond
swiper_angular 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 swiper_angular 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 swiper_angular 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. swiper_angular on npm has been identified as a malicious package (versions 5.9999.0, 5.9999.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011243IN-MAL-2026-014839

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks swiper_angular-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

Explore

All malware advisories How O3 detects malware Vulnerability database