Which versions of @chahuadev/junk-sweeper-app are malicious?

The following npm versions of @chahuadev/junk-sweeper-app are flagged malicious: 2.0.3. Treat any of these as compromised.

How do I remediate @chahuadev/junk-sweeper-app if I installed it?

Remove @chahuadev/junk-sweeper-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @chahuadev/junk-sweeper-app — how do I know if it already compromised me?

If @chahuadev/junk-sweeper-app 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 @chahuadev/junk-sweeper-app part of a known attack campaign?

Yes — @chahuadev/junk-sweeper-app is associated with the IN-MAL-2026-002219 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 @chahuadev/junk-sweeper-app 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 @chahuadev/junk-sweeper-app (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chahuadev/junk-sweeper-app across your stack and pipelines.

Malicious package

@chahuadev/junk-sweeper-appnpm

Malicious code in @chahuadev/junk-sweeper-app (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3682

Immediate action

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

npm uninstall @chahuadev/junk-sweeper-app

What this malware does

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.

Malicious versions

1 flagged

2.0.3

Indicators of compromise (SHA-256)

3d446150767f92344d8d0a699f5879bd746200fb8beb60554408699868f03d51

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @chahuadev/junk-sweeper-app (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chahuadev/junk-sweeper-app across your stack and pipelines.
If you installed it — respond
Remove @chahuadev/junk-sweeper-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @chahuadev/junk-sweeper-app 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 @chahuadev/junk-sweeper-app 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. @chahuadev/junk-sweeper-app on npm has been identified as a malicious package (version 2.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002219

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @chahuadev/junk-sweeper-app-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring