Which versions of dependencyfsdsfdsfg are malicious?

The following npm versions of dependencyfsdsfdsfg are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate dependencyfsdsfdsfg if I installed it?

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

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

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

Malicious package

dependencyfsdsfdsfgnpm

dependencyfsdsfdsfg is a confirmed malicious npm package (MAL-2026-13754) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dependencyfsdsfdsfg (npm)

MAL-2026-13754

Immediate action

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

npm uninstall dependencyfsdsfdsfg

What this malware does

package.json declares postinstall: node index.js, causing index.js to run automatically on npm install. The script collects the installer's username (via whoami), os.hostname(), process.cwd(), and non-internal IPv4 addresses from os.networkInterfaces(), then sends them as query-string parameters via HTTPS GET to the hardcoded endpoint https://xghhv5sajm33m7krgi4n8my0mrsig84x.oastify.com. The *.oastify.com host is a Burp Collaborator out-of-band interaction domain. Package metadata is consistent with a dependency-confusion probe: gibberish name dependencyfsdsfdsfg, version 99.9.0, empty author/description/keywords.

Malicious versions

1 flagged

99.9.0

Indicators of compromise (SHA-256)

c53ad8755f0eb26cef8c05b49cdad8c69b93072e0d9ed176b071a7d367349cab

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

Campaign

IN-MAL-2026-017384

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dependencyfsdsfdsfg-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

Explore

All malware advisories How O3 detects malware Vulnerability database