Which versions of test-dev-config are malicious?

The following npm versions of test-dev-config are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate test-dev-config if I installed it?

test-dev-config 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 test-dev-config — how do I know if it already compromised me?

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

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

Malicious package

test-dev-confignpm

test-dev-config is a confirmed malicious npm package (MAL-2026-13359) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-dev-config (npm)

MAL-2026-13359

Immediate action

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

npm uninstall test-dev-config

What this malware does

src/config.js hardcodes a remote host as the English-word phrase "Four Five P Nine Five P One Eight Six P Two Three Seven" and decodes it at import time via a textToIp() helper to the IPv4 address 45.95.186.237, then exports SOCKET_SERVER_HOST (port 8008) and DJANGO_API_URL (http://45.95.186.237:8000). The word-to-digit encoding serves solely to hide the destination from string and URL scanners. src/constants.js enumerates Chromium, Chrome, Brave, Edge, Opera, and Vivaldi User Data directories under %LOCALAPPDATA%/%APPDATA%, along with Local Storage, leveldb, Local Extension Settings, and Sync Extension Settings paths, the LastPass Chrome extension ID (hdokiejnpimakedhajhdlcegeplioahd), and a KEYLOGGER_DIR ("Results") with a KEYLOGGER_LOG_FILE ("events.log"). The package is the shared configuration layer of a browser-credential-stealer and keylogger toolkit: any consumer importing it inherits the C2 endpoint and the browser-secret target-path list.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

44b80ff2bcf35e5c92c1c8a551b943d334f94793d693ce846707986613db8108

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

Campaign

IN-MAL-2026-015837

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-dev-config-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

Explore

All malware advisories How O3 detects malware Vulnerability database