MAL-2026-3682 Malicious code in @chahuadev/junk-sweeper-app (npm)
Malicious package
Published
MAL-2026-3682 is a malicious package: @chahuadev/junk-sweeper-app (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-3682/ (Markdown: https://insights.sbomify.com/MAL-2026-3682/index.md)
- Package
- @chahuadev/junk-sweeper-app
- Registry
- npm
What is MAL-2026-3682?
MAL-2026-3682 is a malicious package in @chahuadev/junk-sweeper-app, published on 12 May 2026.
Official description
The package's postinstall script (package.json line 10: "postinstall": "node install.js") unconditionally fetches a platform-native executable from https://pub-419d22521da042dfb27d1f404b3eb8a6.r2.dev/Junk-Sweeper.exe or /Junk-Sweeper.AppImage, writes it into the package's bin/ directory, and chmods it 0755 on Linux (install.js lines 10, 14-22, 30-67). No SHA-256, signature, or size verification is performed, and HTTP redirects are followed blindly. The package's bin entrypoint (index.js line 32) then spawnSync's the downloaded binary with the user's argv and inherited stdio, giving the bucket owner a persistent, mutable remote-code-execution channel into any installer machine. The hosting domain is an opaque object-storage bucket, not a versioned release artifact from a transparent source (GitHub Releases with tag pinning, npm registry, etc.). Whether or not the current binary contents are malicious, the delivery mechanism allows the content to be swapped at any time without any version change to the npm package.
What should I do about MAL-2026-3682?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.