registry / Remote code execution / sme-rko-finance-front-operations-fee
sme-rko-finance-front-operations-fee
Common TypeScript definitions
This report shows the evidence for sme-rko-finance-front-operations-fee@35.8.1, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe concrete import-time staged payload chain is independently confirmed in source. Absence of an npm lifecycle hook does not mitigate execution on normal package use.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any Node.js require/import of index.js.
Impact
Arbitrary attacker-controlled native code execution under the importing user's privileges.
Mechanism
remote binary download/DNS staging followed by detached execution
Attack narrative
index.js catches and suppresses errors while importing _vendor.js. That module selects an OS payload, fetches it from concealed Workers hosts or reconstructs it via DNS TXT records, stores it in a temporary directory, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. The package therefore enables attacker-controlled code execution whenever its main entrypoint is imported.
AI rationale
The concrete import-time staged payload chain is independently confirmed in source. Absence of an npm lifecycle hook does not mitigate execution on normal package use.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/package/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _vendor on every package import.
- _vendor.js downloads platform binaries over HTTPS or DNS TXT.
- _vendor.js writes payloads to /var/tmp or Windows Temp, chmods them, then launches detached shells.
- Remote hosts and DNS domains are obfuscated by string concatenation.
- No lifecycle hook is needed: import-time execution makes the attack reachable.
Evidence against
- package.json has no install lifecycle scripts.
- lib/telemetry.js exposes a telemetry API, but the malicious loader is separately auto-imported.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_vendor.jsView file
3const os = require("os");
L4: const https = require("https");
L5: const fs = require("fs");
...
L46: const EXPIRE_SEC = 21357;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L3: const os = require("os");
L4: const https = require("https");
L5: const fs = require("fs");
...
L46: const EXPIRE_SEC = 21357;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L3Findings
2 Critical2 High3 Medium3 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to sme-rko-finance-front-operations-fee@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing sme-rko-finance-front-operations-fee@35.8.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.