# MAL-2026-6167: Malicious code in lazyloading-haptics (npm)


- **Type:** Malicious package
- **Package:** `lazyloading-haptics` (npm)
- **Published:** 17 Jun 2026

## What is MAL-2026-6167?

MAL-2026-6167 is a malicious package in lazyloading-haptics, published on 17 Jun 2026. 

### Official description

The npm package `lazyloading-haptics` (published by npm user `sproger`, slavatopbuyer@gmail.com) is a deceptive React Native component and part of a coordinated 37-package campaign across two attacker-controlled domains (surrprisingcoompanny.lol and barbellmate.xyz). On component mount it registers `appsFlyer.onInstallConversionData` and exfiltrates the app's install/conversion attribution data via `axios.post("https://barbellmate.xyz", data)`, fetches a remote-config URL, and renders it full-screen in a `react-native-webview` that is hidden (display:'none') unless the server returns a valid URL — i.e. App Store review-evasion / attribution-laundering ('cloaking'). The package name is a decoy unrelated to its actual function, and the real logic is concealed behind junk 'calculator' functions with Ukrainian-language comments. Indicators of compromise: C2 surrprisingcoompanny.lol, barbellmate.xyz; npm author `sproger`. Both C2 domains are currently unregistered (dangling-C2 takeover risk for any app still shipping these packages). In this package the payload is obfuscated with obfuscator.io (RC4 string-array); the C2 `barbellmate.xyz` and the exfiltration logic are recoverable by decoding the string array (recovered fragments include 'https://barbellmate.xyz' and 'Error during fetchData').

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

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-6167 is a malicious package: lazyloading-haptics (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-6167/ (Markdown: https://insights.sbomify.com/MAL-2026-6167/index.md)
```

## Sources

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

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