Papers › Single-User Injection for Invisible Shilling Attack against Recommender Systems

Single-User Injection for Invisible Shilling Attack against Recommender Systems

21 Aug 2023arXiv:2308.10467archive 2025-07-28

Chengzhi Huang, Hui Li

Recommendation systems (RS) are crucial for alleviating the information overload problem. Due to its pivotal role in guiding users to make decisions, unscrupulous parties are lured to launch attacks against RS to affect the decisions of normal users and gain illegal profits. Among various types of attacks, shilling attack is one of the most subsistent and profitable attacks. In shilling attack, an adversarial party injects a number of well-designed fake user profiles into the system to mislead RS so that the attack goal can be achieved. Although existing shilling attack methods have achieved promising results, they all adopt the attack paradigm of multi-user injection, where some fake user profiles are required. This paper provides the first study of shilling attack in an extremely limited scenario: only one fake user profile is injected into the victim RS to launch shilling attacks (i.e., single-user injection). We propose a novel single-user injection method SUI-Attack for invisible shilling attack. SUI-Attack is a graph based attack method that models shilling attack as a node generation task over the user-item bipartite graph of the victim RS, and it constructs the fake user profile by generating user features and edges that link the fake user to items. Extensive experiments demonstrate that SUI-Attack can achieve promising attack results in single-user injection. In addition to its attack power, SUI-Attack increases the stealthiness of shilling attack and reduces the risk of being detected. We provide our implementation at: https://github.com/KDEGroup/SUI-Attack.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 10 ran (9 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

kdegroup/sui-attack officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 10 ran (1 instrument-failed) · 4 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran; the contract check could not run
9ran
4unverified

Licence: 1 of the 14 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from kdegroup/sui-attack. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

kdegroup/sui-attack official repository 14 samples, 10 ran (1 instrument-failed) · 4 unverified
calc_loss in 35 papers models/influence/influence_function.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) here; the stored copy is pointer only · 7d9344ac520f8918 · report fixture: signature y:Tensor/2/float, t:Tensor/1/int · returned Tensor · level recorded 2026-09-22
get_param_dict utils.py ran MIT (permissive) · b118561228a8b77b · report fixture: signature model:callable/0/? · returned dict · level recorded 2026-09-24
grad_z in 6 papers models/influence/influence_function.py ran MIT (permissive) · 45e51146ba983e97 · report fixture: signature z:Tensor/2/float, t:Tensor/1/int, model:callable/0/?, gpu:int/0/int · returned list · level recorded 2026-09-24
gumbel_top_k graph.py ran fingerprinted MIT (permissive) · 54320bbdc1da7aa6 · report fixture: signature logits:Tensor/2/float, k:int/0/int, temperature:float/0/float, eps:float/0/float · returned Tensor · level recorded 2026-09-24
load_fake_array utils.py ran MIT (permissive) · 62c0f0f999b06c36 · report fixture: signature file_path:str/0/str, rate:float/0/float · returned csr_matrix · level recorded 2026-09-24
move in 8 papers utils.py ran MIT (permissive) · 02e0131402c87afa · report fixture: signature vars:list/1/Tensor, device:device/0/? · returned tuple · level recorded 2026-09-24
mse_loss in 73 papers
census: 8 implementations from 12 papers, 6 distinct outputs across 4 buckets, one shared input per bucket
models/recommender/WMF.py ran fingerprinted MIT (permissive) · e69b19a3945839ac · report fixture: signature data:Tensor/2/float, logits:Tensor/2/float, weight:float/0/float · returned Tensor · level recorded 2026-09-24
mult_ce_loss models/recommender/WMF.py ran fingerprinted MIT (permissive) · e30156b28108e611 · report fixture: signature data:Tensor/2/float, logits:Tensor/2/float · returned Tensor · level recorded 2026-09-24
save_fake models/baseline.py ran MIT (permissive) · 98f7100e95444343 · report fixture: signature path_save_fake:str/0/str, item_list:list/1/list, shape:tuple/1/int, results_dir:str/0/str · returned str · level recorded 2026-09-24
sparse2tensor models/recommender/RsData.py ran MIT (permissive) · 1ca6bfbc19414e74 · report fixture: signature sparse_data:csr_matrix/2/int · returned Tensor · level recorded 2026-09-24
create_trainvaltest_split data_pre.py unverified MIT (permissive) · 601a1c1306a134de · report
get_loader in 62 papers data_pre.py unverified MIT (permissive) · 2d5a913e453f8011 · report
load_data in 700 papers data_pre.py unverified MIT (permissive) · aeab26784be32147 · report

Tasks

Recommendation Systems

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections