# MAL-2026-3262: Malicious code in react-native-parallax-scroll-view-updated (npm)


- **Type:** Malicious package
- **Package:** `react-native-parallax-scroll-view-updated` (npm)
- **Published:** 29 Apr 2026
- **Also known as:** GHSA-482r-xhg9-23r3

## What is MAL-2026-3262?

MAL-2026-3262 is a malicious package in react-native-parallax-scroll-view-updated, published on 29 Apr 2026. 

### Official description

Dependency confusion and typosquatting campaign by threat actor "saif777". Packages use inflated version numbers (9999.9999.9999, 9999.9999.10000, 50.50.50, 7.66.5) to win version resolution in environments with private registries. All active packages execute a postinstall hook ("node index.js") that collects a system fingerprint — public IP (via api.ipify.org), username, hostname, CPU model, RAM, working directory, OS platform — and exfiltrates it as a Discord embed to a shared webhook (base64-obfuscated in source). Payloads include sandbox/bot detection: machines with ≤1 CPU or <2 GB RAM are flagged as sandbox/CI; real machines trigger a green embed. Typosquats the react-native-parallax-scroll-view package.

The package react-native-parallax-scroll-view-updated was found to contain malicious code.

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.

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

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-3262 is a malicious package: react-native-parallax-scroll-view-updated (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-3262/ (Markdown: https://insights.sbomify.com/MAL-2026-3262/index.md)
```

## Sources

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

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