Which versions of dcfarguscert are malicious?

The following npm versions of dcfarguscert are flagged malicious: 999.0.1. Treat any of these as compromised.

How do I remediate dcfarguscert if I installed it?

dcfarguscert establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed dcfarguscert — how do I know if it already compromised me?

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

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

Malicious package

dcfarguscertnpm

dcfarguscert is a confirmed malicious npm package (MAL-2026-13753) that opens a backdoor for remote access (malicious version 999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dcfarguscert (npm)

MAL-2026-13753

Immediate action

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

npm uninstall dcfarguscert

What this malware does

[email protected] registers both preinstall and postinstall lifecycle scripts that invoke src/telemetry.js. On install, telemetry.js collects host identifiers (os.hostname(), os.userInfo().username, OS release, process.platform, process.arch, Node version, CI flag) and the output of npm ls -g --depth=0 --json (the installer's globally installed npm package inventory), then POSTs the aggregated payload over plain HTTP to the hardcoded endpoint http://16-171-38-148.sslip.io:8080/api/install (bare IP 16.171.38.148 encoded via sslip.io). The version number 999.0.1 and the package description referencing a 'dependency test' with 'check ips' are consistent with a dependency-confusion beacon that fires unconditionally on install without any user consent or opt-out.

Malicious versions

1 flagged

999.0.1

Indicators of compromise (SHA-256)

6b0841cccc5aa4961351a4cf991d7744a1d7acc4da3824321fed50e1e7b8657d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dcfarguscert (version 999.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dcfarguscert across your stack and pipelines.
If you installed it — respond
dcfarguscert establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dcfarguscert 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 dcfarguscert 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. dcfarguscert on npm has been identified as a malicious package (version 999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017385

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dcfarguscert-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database