Which versions of filter-imports are malicious?

The following npm versions of filter-imports are flagged malicious: 8.0.3. Treat any of these as compromised.

How do I remediate filter-imports if I installed it?

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

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

Yes — filter-imports is associated with the GHSA-j542-xg84-95px 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 filter-imports 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 filter-imports (version 8.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging filter-imports across your stack and pipelines.

Malicious package

filter-importsnpm

Malicious code in filter-imports (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1327

Immediate action

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

npm uninstall filter-imports

What this malware does

The package 'filter-imports' is part of the PhantomRaven supply chain attack campaign (Wave 4). It uses a Remote Dynamic Dependency (RDD) technique: the published package appears benign but includes a URL-based dependency in package.json pointing to an attacker-controlled C2 server (npm.artifactsnpm.com). During npm install, npm automatically fetches a malicious tarball from the C2. The tarball preinstall hook executes a 259-line payload that harvests developer emails from .gitconfig, .npmrc, and environment variables; collects CI/CD tokens from GitHub Actions, GitLab CI, Jenkins, and CircleCI; fingerprints the host system; and exfiltrates all data to http://npm.artifactsnpm.com/npm.php via redundant HTTP GET, POST, and WebSocket channels with no visible terminal output. The campaign was first disclosed by Koi Security in October 2025 (Wave 1) and extended across Waves 2-4 between November 2025 and February 2026. Full analysis: https://www.endorlabs.com/learn/return-of-phantomraven

Any developer or CI/CD system that installed this package should be considered compromised. All secrets, tokens, and credentials accessible from that environment should be rotated immediately from a separate, unaffected machine.

The package filter-imports 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.

Malicious versions

1 flagged

8.0.3

Indicators of compromise (SHA-256)

a4e874a4a0c768fc14ad3fdadda8a7816bcc0c1b437c0fcc3ae11c3b42c1f5b6

af91e96f3e3e13924a3b768387b6562c76edf886e90526b14843084dfca83677

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

Campaign

GHSA-j542-xg84-95px

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks filter-imports-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